10.1

•
Set cacheFolderContextFile to the path of the "cache.xml" file relative to the current
working directory.
•
Set serverXmlFilePath to the path of the "Server.xml" file relative to the current working
directory.
8
Open the file [Tomcat_Home]/conf/Catalina.properties and specify the path of the
shared class loader. For example:
shared.loader=${catalina.home}/qxpsm/lib/*.jar,${catalina.home}/conf
9
Open the file [Tomcat_Home]/conf/Catalina/localhost/cache.xml and set the
docbase attribute to the path of the appropriate cache folder.
10
Double-click the "startup.sh" shell file (Mac OS) or the "startup.bat" file (Windows). These
files can be found in the TOMCAT_HOME/bin folder.
Deploying QXP Server in WebSphere
To install QuarkXPress Server as an independent Web application in an IBM WebSphere
Web container:
1
Locate the QuarkXPress Server installation folder (referred to here as [QXPS-BUILD]).
2
Navigate to the administrative console page for your server and log in.
3
Under Applications, click New Application.
4
Click New Enterprise Application.
5
Upload the [QXPS_BUILD]\QXPS-EAR\qxps-9.5.ear file and begin installing it using
the default options.
6
On the Map modules to servers page, check QuarkXPress Server. If you want to also
install the admin interface, also check qxpsadmin.
7
On the Map virtual hosts for Web modules page, check QuarkXPress Server. If you want
to also install the admin interface, also check qxpsadmin.
8
Complete the installation in the WebSphere admin client. Be sure to save your changes
to the master configuration.
9
Locate the WebSphere installation folder for your profile (for example, C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01). This location will be referred
to here as [WebSphere_Home].
10
Copy the [QXPS_BUILD]/conf folder to the [WebSphere_Home] directory.
11
In the [WebSphere_Home] directory, open the file conf/ServerApp.properties and
make the following changes:
•
qxpswebserver.embeddedwebcontainer=false
•
qxps.webapp.context.name=/qxps
16 | QUARKXPRESS SERVER 10.1 README
DEPLOYING IN AN EXTERNAL WEB CONTAINER