<Application> Properties, General Tab
Use the <Application> Properties and New Non-Commerce ApplicationProperties dialog boxes, General tab,to view or modify the properties of an application or configure a non-Commerce application. When you configure an application, you specify properties that apply to all the Web servers that the application uses.
Note
After you change a property in Commerce Server Manager, you must restart all services that use those properties.
Use this |
To do this |
|---|---|
Application Name |
Type the application name for the new non-Commerce application. .gif "Note") Note:
If you are viewing an existing application, this field is disabled and labeled Display name.
|
Web servers in this application are running IIS |
Select if the servers in the non-Commerce application are running Internet Information Services (IIS) 5.0. You cannot have both IIS and non-IIS servers in a non-Commerce application. |
Nonsecure host name |
Type the Domain Name System (DNS) to use for non-secured links in your applications. .gif "Caution note") Caution:
If you use a port number other than 80, you must append that number to the end of the nonsecure host name, for example, www.microsoft.com:81. To view or change the port number, see the TCP Port box on the Identities tab in the Web Server Properties dialog box. For more information, see How to Configure a Web Server.
|
IIS application path |
Type the path of the IIS application. |
Application path |
If no Web servers in this application are running IIS, type the path of the application. |
Enable HTTPS |
Select to enable links to a secure HTTP host (Secure Sockets Layer (SSL)) in your applications. Note:
The AuthManager Object uses the Enable HTTPS and Secure host name options; AuthFilter does not use them. If you use AuthFilter, use the site's CS Authentication resource Login Form property to specify SSL for logon pages. For more information about AuthManager, see What Is AuthManager?
|
Secure host name |
Type the DNS domain name to use for secured links in your applications. Caution:
If you use a port number other than 443, you must append that number to the end of the secure host name, for example, www.microsoft.com:441. To view or change the SSL port number, see the SSL Port box on the Identities tab in the Web Server Properties dialog box. For more information, see How to Configure a Web Server.
|
Autocookie |
Select this property to generate cookies for anonymous users. This property is set during the unpacking process. |
Authentication filter |
Important Note:
We provide this field for backwards compatibility with earlier versions of Commerce Server 2009 R2 that use AuthManager or AuthFilter (an Internet Server API (ISAPI) filter) to manage user authentication and identification. The selection you make is only referenced if you use one of these methods for user authentication. For information about AuthManager, see What Is AuthManager? For information about AuthFilter, see What Is AuthFilter?For more information about Commerce Server 2009 R2 authentication for Web applications, see Authentication Concepts and Tasks.
From the drop-down list, select the type of authentication filter you want to use. The options are as follows:
|
Set cookie path to Application |
Select this option if you want to share cookies among the applications in a site. |
Number of shared domain levels |
Specify how many domain levels applications need in common in order to share a cookie. For example, for premier.microsoft.com and msn.microsoft.com to share the microsoft.com cookie, set the value to 2. |
Generate New Encryption Key |
Click to generate a new cookie encryption key. You use this new cookie encryption key to encrypt cookies (tickets) that the CS Authentication module issues. If you are using Commerce Server Membership Provider, then you do not need to generate new cookie encryption keys. Important Note:
If you are using CS Authentication, do not change encryption keys while the site is active because it invalidates all currently issued tickets, forcing users to login again.Before you update an existing encryption key, we recommend that you store the existing encryption keys where your application can retrieve them. Commerce Server 2009 R2 does not create a backup for you. We recommend that you back up the key to a secure location; preferably to a location that users cannot access.
|
See Also
Other Resources
What Is the Commerce Server Membership Provider?
How to Add an Application to a Site