This chapter covers the technical issues of:
 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Technical RequirementsThis document lists the supported client and server platforms for CRX. Day provides several levels of support, both for our recommended configurations and for other configurations. Please refer to the Installation Guide for detailed instructions and notes for installing and runninng CRX on the supported platforms.
Recommended Configurations Day recommends these configurations and provides full support as part of the standard software maintenance agreement. The configuration is tested and known bugs are fixed. Issues that are submitted by customers in the form of a fully qualified request are addressed in future releases.
Note Note: In previous releases, Day used three different support levels for the fully supported configurations (A,B,C). Currently the supported platforms are all on level A. Configurations with Optional Support Agreement Day expects these platforms to work. Support is available as an optional add on to the standard software maintenance agreement.
Unsupported Configurations
CRX works with the following server platforms:
CRX works with virtual machines in the following cloud computing environments:
CRX running in virtual machines in the cloud computing environments is supported in compliance with Day's support policy for all other system components (operating system, JVM, application server, etc). CRX works with the following Java Runtime Environments (JREs):
CRX works with the following client platforms.
CRX runs on the following application servers. You can run CRX without an application server, but you need a Servlet Engine. CRX ships with Day’s Servlet Engine, formerly known as CQSE, which you can use freely and which is fully supported.
The following platforms are supported for the Dispatcher, Day’s caching and load balancing solution:
This section provides special notes and more detailed information about running CRX on certain platforms.
Windows 2003 Windows 2003 with SP2 cannot connect to WebDAV. See Microsoft - Software Update for Web Folders (KB907306) for full details of the manual updates that need to be made. Windows Vista Windows Vista requires SP2 to connect to WebDAV. To successfully connect with Vista SP2, basic authentication for webclients must be enabled. This requires a change in the windows registry to enable basic authentication on the client computer:
See Microsoft Support KB 841215.
Note Java Distributions. The CRX application requires only a Java Virtual Machine to run, which is provided by the Java Runtime Environment (JRE) distribution. Generally Day recommends using the Java Development Kit (JDK) distribution, which is a typical requirement of the Java application servers in which CRX runs. Both JRE and JDK distributions are a part of the Java Standard Edition (Java SE). Note Java Environment Suppliers. The IBM and HP Java environments are only supported on IBM and HP server platforms, respectively. For all non-IBM, non-HP platforms, the Sun JRE is supported. Note Servlet API Versions. CRX Launchpad web development environment, based on Apache Sling, requires a servlet engine supporting Servlet API version 2.4. All other components of CRX, including the JCR repository and CRX web application, also work with servlet engines supporting Servlet API version 2.3. Note Application Server Support. CRX is expected to work with any modern application servers/servlet engines (that support at least Servlet API 2.3), including popular open source products like Jetty, Apache Tomcat, Apache Geronimo or Sun GlassFish. Day recommends stable, non-deprecated versions of these application servers (information available on supplier websites). For production use, Day offers optional support for these platforms. To install a CRX instance, you need the following:
The prerequisites above state the minimum, which is needed to start install or start a default repository. The actual resource requirements differ vastly depending on the configuration, applications running on top of the repository, or executed use cases. Please note that you might need to start the installer with customized memory settings if you have very little free memory, as the default Quickstart memory settings are configured to allow for more flexibility in deploying bigger content applications on top of the repository. Note Note: The JRE is not bundled with CRX. You can obtain JRE 1.5 or higher from the Sun web site. Note CRX Quickstart requires create and write privileges within the installation directory. Ensure that the user installing CRX has these privileges for the chosen directory. The CRX repository consists of two parts:
Day recommends that you use the tar persistence manager, which is preferred. If you install the two parts on separate computers (for example if you use your central database server for persistent storage, or if you run Tar persistence manager on a networked storage device, like SAN or NAS), make sure that the CRX instance has excellent network access to the repository. Lags or elongated response times in the communication between the CRX instance and the persistent storage may cause severe performance issues. If you use a database persistence manager to store the CRX data in an external database (that is, a database on a server that runs independently from CRX), you need to set up the database before installing CRX. By default, CRX uses the tar persistence manager. If you need to configure a database persistence manager, see Custom Installation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Forgotten your password? Reset the password here.
Note: Customers with DayCare user accounts need to create a new account for use on day.com.