The SAS Content Server is a content
repository that stores digital content (such as documents, reports,
and images) created and used by SAS client applications. Examples
of such content include reports and documents created by users of
SAS Web Report Studio and the SAS Information Delivery Portal.
The Web-based Distributed
Authoring and Versioning (WebDAV) protocol is currently the main method
used to access the SAS Content Server. In addition to the basic features
of HTTP, the WebDAV protocol is an extension to HTTP and provides
Write access, version control, search, and other features.
The SAS Content Server
starts automatically when the Web application server is started and
depends on the SAS Services Application. The SAS Services Application
deploys a set of services called Remote Services that are used by
SAS Information Delivery Portal, the SAS Stored Process Web application,
and other Web applications. The SAS Services Application must be started
before you start your Web application server.
Three JVM options are
related to the SAS Content Server deployment. In the event that the
deployment of SAS Content Server changes, the JVM options can be used
to set the new values.
SAS Content Server JVM Options
|
|
|
|
|
|
|
|
Use the host name of
the Web application server.
|
|
|
Use the port number
of the Web application server instance.
|
For deployments that
use WebSphere Application Server with approximately 900 concurrent
users, you can avoid performance issues and transaction time out errors
by modifying the JDBC data source definition. Use the administration
console to modify the SharedServices data source with a connection
pool custom property. Add a custom connection pool property with a
name of
defaultConnectionTypeOverride and
a value of
unshared.