The iPlanet Application Server Customizer

iAS (WAR)

You use the iAS tab to configure the web application targeted to your operational iAS environment.

For example, iAS supports single sign-on for multiple web applications. You can create multiple applications where the user needs to log on (be authenticated) only once. A scenario for this feature could be a consolidated airline booking service which searches all airlines and provides links to different airline web sites. Once the user is authenticated on the consolidated booking service, the log on information can be used by each of the individual airline sites, without requiring the user to log on again.

Field/Column

Explanation

Distributed Session

If checked, a session can be distributed across multiple iAS machines.
A session can be either a distributed fault-tolerant session, or a lightweight local-only session. Local only sessions are available locally in one engine, and have to depend upon requests being sticky (See Using the Deployment Descriptors for Servlets/JSPs). In addition, local only sessions have no fault-tolerance if the engine crashes.

Secure Session

If checked, the session can only occur on a secure (HTTPS) server.

TimeOut(seconds)

Enter a period in seconds that specifies when the client is no longer active. If unspecified, a system-wide default session timeout of 30 minutes is used.

Timeout Type

Specify when the timeout count begins: since last access or since session creation.

Data Synchronization

If you specified a distributed session on this tab, then select the session type: "dsync-local" or "dysnc-distributed". DSync distributed helps failover across instances of the application server participating in a cluster.

Domain (supports single sign-on

Enter the domain to which the cookie is sent back from the web browser. By default, the domain of the URL that sets the cookie is assumed to be the domain where the cookie is sent back. You can specify a different domain here, if needed.

Path (supports single sign-on)

Enter the path for the session cookie (i.e. the minimum path that the URL must have for the cookie to be sent back from the browser. For example, setting the path to /phoenix, will send the cookie back when either of the following URLs are accessed:
http://my.foo.com/phoenix/bees.htm
http://my.foo.com/phoenix/birds.htm
The path must begin with "/". If the path is not set, then the default path is assumed to be that of the URL setting the cookie.

Scope (supports single sign-on)

A grouping name that identifies applications participating in single sign-on. Each application participating in a single sign-on for a grouping of applications must use the same grouping name.
For example applications such as "login", "homeBanking", "loanCenter" within the same application server cluster, can share a session by specifying the same scope variable, "myBank."

See also
	Using the Deployment Descriptors for Servlets/JSPs

Legal Notices

Field/Column	Explanation
Distributed Session	If checked, a session can be distributed across multiple iAS machines. A session can be either a distributed fault-tolerant session, or a lightweight local-only session. Local only sessions are available locally in one engine, and have to depend upon requests being sticky (See Using the Deployment Descriptors for Servlets/JSPs). In addition, local only sessions have no fault-tolerance if the engine crashes.
Secure Session	If checked, the session can only occur on a secure (HTTPS) server.
TimeOut(seconds)	Enter a period in seconds that specifies when the client is no longer active. If unspecified, a system-wide default session timeout of 30 minutes is used.
Timeout Type	Specify when the timeout count begins: since last access or since session creation.
Data Synchronization	If you specified a distributed session on this tab, then select the session type: "dsync-local" or "dysnc-distributed". DSync distributed helps failover across instances of the application server participating in a cluster.
Domain (supports single sign-on	Enter the domain to which the cookie is sent back from the web browser. By default, the domain of the URL that sets the cookie is assumed to be the domain where the cookie is sent back. You can specify a different domain here, if needed.
Path (supports single sign-on)	Enter the path for the session cookie (i.e. the minimum path that the URL must have for the cookie to be sent back from the browser. For example, setting the path to /phoenix, will send the cookie back when either of the following URLs are accessed: http://my.foo.com/phoenix/bees.htm http://my.foo.com/phoenix/birds.htm The path must begin with "/". If the path is not set, then the default path is assumed to be that of the URL setting the cookie.
Scope (supports single sign-on)	A grouping name that identifies applications participating in single sign-on. Each application participating in a single sign-on for a grouping of applications must use the same grouping name. For example applications such as "login", "homeBanking", "loanCenter" within the same application server cluster, can share a session by specifying the same scope variable, "myBank."