How it Works
Quark
Loading...
A
D
G
K
L
M
O
P
Q
Loading...
Loading...
Publishing Platform 2015
Upgrade Paths
27 pgs239.62 Kb0
Manuel de mise à jour (Février 2016) [fr]
237 pgs10.62 Mb0
Operating Guide
218 pgs26.85 Mb0
Manuel de mise à niveau [fr]
28 pgs244.83 Kb0
Table of contents
Loading...

Quark Publishing Platform 2015 Administrator’s Guide

Quark Publishing Platform 2015 System Administration Guide

CONTENTS

Contents
Introducing Quark Publishing Platform administration tasks.......6
Deploying Quark Publishing Platform Server to External Server Containers.7
Setting up environment variables.....................................................................7
Configuring the JVM.........................................................................................7
Deploying in IBM WebSphere...........................................................................8
Deploying in Oracle WebLogic..........................................................................9
Deploying in external Tomcat.........................................................................10
Requirements and setup.........................................................................................11
Setup Tomcat running on Windows........................................................................11
Server startup and verification.................................................................................13
Deploying Quark Publishing Platform Server in multi-server deployment.....14
Configuring IIS as an HTTP load balancer...............................................................16
Configuring Apache Web Server as an HTTP load balancer...................................18
Configuring server caches flushing mechanism......................................................19
Enabling Secure Sockets Layer (SSL) for Quark Publishing Platform Server.21
SSL support.....................................................................................................21
Enabling SSL in Quark Publishing Platform Server..................................................21
Configuring Platform clients to log on to an SSL enabled Server...........................22
Verifying and using SSL...........................................................................................23
Quark Publishing Platform Server — Manual configuration
...................................................................................................24
Editing "ServerApp.properties".....................................................................24
Editing "PublishingPool.properties"...............................................................25
Configuring Quark Publishing Platform Renderer for Quark Publishing Platform usage.26
Editing "Qla.properties".................................................................................26
Extended configuration files...........................................................................26
Configuring Platform Server to be used for publishing with Quark XML Author - Sharepoint Adapter.27 Configuring Platform Server to be used for publishing with Quark XML Author - FileNet Adapter.27
JVM memory allocation on Windows..............................................................27
Using Quark Publishing Platform Server Console or Quark Publishing Platform Server Windows service.28
Using "Serverstartup.bat".......................................................................................28
Configuring Windows authentication..............................................................28
Steps to enable SSO in Platform Clients.................................................................29
ii | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
CONTENTS
Steps to configure Web Client for mixed mode authentication.............................30
Configuring logging levels..............................................................................31
Changing logging levels in "log4j.xml"..................................................................31
Changing logging levels after starting Quark Publishing Platform Server..............31
Changing logging for exceptions............................................................................32
Modifying search notification evaluation settings..........................................32
Database properties........................................................................................34
Transformation properties..............................................................................35
Session timeout...............................................................................................36
Repository status updater...............................................................................36
Using Kerberos authentication................................................................................37
Using Simple authentication...................................................................................38
Connecting LDAP user passwords with Quark Publishing Platform Server.............38
Restricting Workspace Browser palettes........................................................39
Changing query results settings......................................................................39
Controlling delivery channel display settings in Web Client...........................40
Changing case-sensitivity for Quark Publishing Platform passwords.............41
Managing filters and index service settings ...................................................41
Index service settings..............................................................................................42
ASPOSE filter...........................................................................................................42
APS filter..................................................................................................................44
POI filter..................................................................................................................44
QuarkXPress Server Filter........................................................................................45
JAWS filter settings.................................................................................................46
XML Author filter settings.......................................................................................46
Full text indexing configuration......................................................................47
Charting Service..............................................................................................47
Enabling IPTC support.....................................................................................48
RMI and CORBA clients only...........................................................................49
Changing ports used by Quark Publishing Platform Server....................................49
Multiple network cards............................................................................................50
Firewalls with NAT...................................................................................................51
Failover setup..................................................................................................51
Encrypting a plain text password...................................................................55
Configuring WebAdmin to enable forced log off...................................................56
Configuring Workspace to enable forced log off....................................................57
Configuring messaging....................................................................................58
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | iii
CONTENTS
Quark Publishing Platform Web Client: Manual configuration...59
Configuration overview...................................................................................59
Application level settings................................................................................59
Multi-Channel preview....................................................................................61
Attrbutes for General pane.............................................................................62
Role based Toolbar configuration...................................................................63
Restricting access to Web Client/Admin.........................................................65
Quark Publishing Platform Clients — Manual configuration......67
Creating and maintaining the log file (Mac OS X only)...................................67
Creating and maintaining the log file (Windows only)....................................67
Creating and maintaining the log file (Quark XML Author for Platform)........69
Suppressing the accessibility services warning - Mac OS X............................70
Displaying revision comments.........................................................................70
Displaying first and last names........................................................................70
Changing the preview font and size (Windows only)......................................71
Setting maximum number of assets to be fetched (Windows only)................72
Specify whether to use Chunked Encoding (Windows only)...........................72
Specify support for lazy loading when searching (Windows only)..................72
Setting the service time out values for all remote service references (Windows only).73
Setting the service timeout value for publishing service (Windows only)......73
Specify the font size of the copy tasting row (Windows only)........................73
Specify the icon for a file extension (Windows only)......................................73
Controlling password retention (Mac OS X only)............................................74
Using Mac clients with a proxy server............................................................74
Using Windows clients with a proxy server....................................................75
Mirroring the collection hierarchy on Check Out/Get.....................................75
Turning off collection mirroring: Mac OS X.............................................................75
Turning off collection mirroring: Windows..............................................................75
Configuring publishing channels.....................................................................76
Configuring publishing channels: Windows............................................................76
Configuring Delivery Channels........................................................................77
Configuring delivery channels: Windows................................................................77
Setting preferences for Quark XML Author for Platform...............................78
Setting the Check out location................................................................................78
Setting the file deletion preference on Save and Close..........................................78
Setting the quick search preference........................................................................78
Configuring the Platform Adapters for Microsoft Office components for web sharing.79
Configuring the Quark Publishing Platform Adapter for Microsoft Office - Word...80 Configuring the Quark Publishing Platform Adapter for Microsoft Office - Excel...80 Configuring the Quark Publishing Platform Adapter for Microsoft Office - PowerPoint.80
iv | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
CONTENTS
Update published ClickOnce deployments............................................................80
Manual configuration for QuarkXPress and QuarkCopyDesk XTensions........83
Managing backups and file storage............................................84
Backing up your database.......................................................................................84
Backing up assets....................................................................................................84
Backing up Index files (full text search)...................................................................84
Restoring Quark Publishing Platform Server..................................................85
Restoring Assets......................................................................................................85
Restoring Full Text Indexes.....................................................................................85
Legal notices...............................................................................87
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | v

INTRODUCING QUARK PUBLISHING PLATFORM ADMINISTRATION TASKS

Introducing Quark Publishing Platform administration tasks
Administering a Quark® Publishing Platform™ environment requires extensive
hardware and software maintenance in addition to the controls in Quark Publishing
Platform. This guide describes tasks administrators perform for security, system
configuration adjustments, and integration with other systems. For information about
administrating in the Quark Publishing Platform interface, see A Guide to
Quark Publishing Platform. For information about installing Quark Publishing Platform
software, see the Quark Publishing Platform ReadMe.
6 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE

DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS

Deploying Quark Publishing Platform Server to External Server Containers
You can deploy Quark Publishing Platform Server in an external Tomcat installation,
in IBM WebSphere, and in Oracle WebLogic.

Setting up environment variables

To prepare for deployment, set the following environment variables.
If you are deploying Quark Publishing Platform Server as a service, you must set these
as global system environment variables.
•
MAGICK_HOME: [ImageMagick installation directory]\bin
•
MAGICK_FILTER_MODULE_PATH: %MAGICK_HOME%/modules/filters
•
MAGICK_CODER_MODULE_PATH: %MAGICK_HOME%/modules/coders

Configuring the JVM

Regardless of which application server you are using, you must increase the memory
available to the JVM in Tomcat, IBM WebSphere and Oracle Weblogic as follows to
accommodate Quark Publishing Platform Server:
• Set the minimum Java heap memory to 1536MB.
• Set the minimum PermGenSpace to 512MB.

Preparing the EAR file for deployment

A Platform EAR build consists of the following things:
• Platform Server Configuration files.
• Binaries of dependencies.
• A tool to generate the JEE EAR file.
The following folders are included in an EAR build:
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 7
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
•
conf: Contains Platform Server configuration files.
•
database: Contains database creation, update, and support files.
•
ImageMagick: Contain ImageMagick application binaries.
•
Jaws: Contains JAWS application binaries.
•
DITA-OT1.6: Contains DITA OT binaries.
•
publishing: Contains configuration and resource files for the Quark Publishing
Platform framework.
The Platform Server application consists of following modules:
•
admin.war: The Quark Publishing Platform administration Web application.
•
workspace.war: The Quark Publishing Platform workspace Web application.
•
webservices.war: The Quark Publishing Platform Server Web services module.
•
rest.war: The Quark Publishing Platform server REST interface module.
•
messaging.war: The HTTP-based messaging interface.
•
qxpsm.war: QuarkXPress Server Manager.
•
qxpsmadmin.war: The QuarkXPress Server Manager administration Web application.
To generate the Quark Publishing Platform Server JEE enterprise archive:
Copy the Quark Publishing Platform EAR build to the computer on which the
1
application server is running.
Update the configuration files (including "Database.properties", "managerconfig.xml",
2
"PluginContext.xml", and "QLA.properties.xml") as described in "Quark Publishing
Platform Server — Manual configuration ."
Update the values for the JMX Agent username and password in "serverApp.properties".
3
The values for username and password will be the same used to log on to WebSphere's
admin console.
Run RunEARUpdater.bat. A "For Deployment" folder is created, containing a
4
deployable Quark Publishing Platform EAR file.

Deploying in IBM WebSphere

To deploy in IBM WebSphere (Supported version is 8.5.5.4):
Copy the "qpp" folder from "For Deployment" to the working directory of the
1
application server instance where the EAR file will be deployed. For IBM WebSphere,
this is typically the folder corresponding to the target profile.
To deliver resources (Quark Publishing Platform or otherwise) to IBM FileNet, add the following to the end of the [working directory]\properties\wsjaas.conf file:
FileNetP8WSI { com.filenet.api.util.WSILoginModule required; };
8 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
Launch the IBM WebSphere application server console by navigating to
2
http://localhost:port/ibm/console.
Under Applications, click New Application.
3
Click New Enterprise Application.
4
Under Path to the new application, click Choose File and then select the .ear file in
5
the "For Deployment" folder. (For more information, see "Preparing the EAR file for
deployment.")
Under Preparing for the application installation, click Next.
6
Click Next for steps 1, 2, 3, and 4. Leave all settings at their default.
7
Click Finish for step 5.
8
Click Save.
9
Navigate to Applications > Application Types > WebSphere enterprise applications
10
and click qpp-server-11.0.ear.
Click Class loading and update detection.
11
Under General properties > Class loader order, click Classes loaded with local class
12
loader first (parent last).
Click Save to save all changes.
13
Navigate to Applications > Application Types > WebSphere enterprise applications
14
and click qpp-server-11.0.ear again.
Under References, click Shared library references.
15
Check the box next to qpp-server-11.0.ear, then click Reference shared libraries.
16
On the next screen, click New.
17
Select any name. As classpath, enter the relative paths of the Platform publishing and
18
ext folders.
For example, to target this directory:
C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01\qpp\publishing
...you would enter ./qpp/publishing and ./qpp/ext
Click Apply or OK to save the settings.
19
Assign this library reference to the qpp-server-11.0.ear application.
20
Start the qpp-server-11.0.ear Web application.
21
To verify the installation, navigate to the following URLs:
22
http://localhost:9080/admin http://localhost:9080/workspace

Deploying in Oracle WebLogic

To deploy Quark Publishing Platform Server in Oracle WebLogic (supported version
is 12.1.3):
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 9
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
Start the WebLogic server.
1
Create a new WebLogic domain named QPP_DOMAIN.
2
To set the JVM parameter for specifying the location of the "krb5.conf" file, open the
3
file [WEB_LOGIC _DIR]\domains\base_domain\bin\setDomainEnv.cmd and
append the following to the end:
set JAVA_OPTIONS=%JAVA_OPTIONS%
-Djava.security.krb5.conf=./qpp/conf/krb5.conf
Copy the "qpp" folder from the "For Deployment" folder to the target WebLogic server
4
domain directory (for example,
C:\oracle\Middleware\user_projects\domains\QPP_DOMAIN).
Set the global system environment variable CLASSPATH on the WebLogic computer
5
to the following value:
[WEB_LOGIC_DIR]\domains\QPP_DOMAIN\qpp\publishing
and
[WEB_LOGIC_DIR]\domains\QPP_DOMAIN\qpp\ext
Restart WebLogic.
6
Open the Oracle Weblogic application server console using the following URL:
7
http://localhost:port/console
Select the domain (QPP_DOMAIN), then click the Web Applications tab.
8
Check Archived Real Path Enabled.
9
Click Save.
10
Under Domain Structure, click Deployments.
11
Under Deployments on the right, click Install and supply the path of the .ear file in
12
the "For Deployment" folder. (For more information, see "Preparing the EAR file for
deployment.")
In the next screen, click Next with the default option (Install this deployment as an
13
application) selected.
In the next screen, click Next.
14
Click Finish.
15
Click Save.
16
Start the Quark Publishing Platform Web application.
17
To verify the installation, navigate to the following URLs:
18
http://localhost:7001/admin http://localhost:7001/workspace

Deploying in external Tomcat

Developed by the Apache Software Foundation, Apache Tomcat™ serves as the standard reference implementation for Java™ Servlet and JavaServer™ Pages technologies. Tomcat™ is a servlet container for managing Web applications.
10 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
When you install the standalone version of Quark Publishing Platform Server, the
installation embeds an instance of Tomcat in the Quark Publishing Platform Server Java Virtual Machine (JVM™) to manage Quark Publishing Platform Web applications,
such as Quark Publishing Platform Web Client.
However, if you are already running a Tomcat server for other Web applications, and
you want the Quark Publishing Platform Web applications to use your existing Tomcat
server, you can deploy Quark Publishing Platform Server in this instance of Tomcat.
Deploying Quark Publishing Platform Server in your existing (that is, external) Tomcat
server means you don't have to run a separate Quark Publishing Platform Server process
on the server computer. If you want to deploy Quark Publishing Platform Server in
your external Tomcat, you can use a separate build located in "Server (External Web
Container)" in your software package.

Requirements and setup

Quark Publishing Platform Server requires JAVA 7 and Apache Tomcat 7.0.61 or above
to be configured as a Web server. The computer on which Tomcat is running should
be a 64-bit computer. You can add Quark Publishing Platform Server to an existing
Tomcat installation.

Setup Tomcat running on Windows

The existing Apache Tomcat installation folder in the steps below is TOMCAT_HOME
To deploy Quark Publishing Platform in an external Tomcat installation created by
the Tomcat installer or deployed with binaries:
Copy the [QPP_BUILD]/qpp folder to the [TOMCAT_HOME] folder.
1
Copy the contents of the [QPP_BUILD]/webapps folder to the
2
[TOMCAT_HOME]/webapps folder.
If a [TOMCAT_HOME]/endorsed folder does not exist, create this folder.
3
Copy the contents of the [QPP_BUILD]/endorsed folder to the
4
[TOMCAT_HOME]/endorsed folder.
If Tomcat is installed with the installer, in the
5
[TOMCAT_HOME]/qpp/publishing/AS-Busdoc.xslt, [TOMCAT_HOME]/qpp/publishing/BusDoc2QCD.xslt, [TOMCAT_HOME]/qpp/publishing/BusDoc2QXPS.xslt and [TOMCAT_HOME]/qpp/publishing/SmartDoc2QXPS.xsltfiles, update the following
paths as given below:
<xsl:include href="./qpp/publishing/xref-dita-anchors.xslt"/> <xsl:include href="./qpp/publishing/AS-StyleSheets.xslt"/> <xsl:include href="./qpp/publishing/AS-Transformations.xslt"/> <xsl:include href="./qpp/publishing/BusDocsWordTableStyles.xslt"/>
If Tomcat is deployed with binaries, in the
6
[TOMCAT_HOME]/qpp/publishing/AS-Busdoc.xslt, [TOMCAT_HOME]/qpp/publishing/BusDoc2QCD.xslt, [TOMCAT_HOME]/qpp/BusDoc2QXPS.xslt and
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 11
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
[TOMCAT_HOME]/qpp/publishing/SmartDoc2QXPS.xslt files, update the following
paths:
<xsl:include href="../qpp/publishing/xref-dita-anchors.xslt"/> <xsl:include href="../qpp/publishing/AS-StyleSheets.xslt"/> <xsl:include href="../qpp/publishing/AS-Transformations.xslt"/> <xsl:include href="../qpp/publishing/BusDocsWordTableStyles.xslt"/>
In the [TOMCAT_HOME]/qpp/conf/ServerApp.properties file:
7
•
Enter the webServer.port value you configured for Tomcat (8080 for example).
•
Set the webServer.embeddedWebContainer value to false.
In the [TOMCAT_HOME]/qpp/conf/ManagerConfig.xml file:
8
•
Enter the IP address or hostname of the QuarkXPress Server in the name element of the connectioninfo section.
•
Enter the port for QuarkXPress Server in the port element.
Keep in mind that your Tomcat and the QuarkXPress Server should not be running
on the same port if QuarkXPress Server and Tomcat are running on the same machine.
In the [TOMCAT_HOME]/qpp/conf/Qla.properties file:
9
• Set the host name, port number, and serial number of your instance of the QLA
Server.
To configure the database, in the [TOMCAT_HOME]/qpp/conf/Database.properties
10
file edit/add the following values:
• For Oracle:
qpp.jdbc.driverClassName = oracle.jdbc.driver.OracleDriver qpp.jdbc.url = jdbc:oracle:thin:@<hostname><:portnumber><:oracle_sid> qpp.jdbc.userName = QppOracleDB qpp.jdbc.password = QppPassword
• For SQL Server:
qpp.jdbc.driverClassName = com.microsoft.sqlserver.jdbc.SQLServerDriver qpp.jdbc.url =jdbc:sqlserver://<your-host-name>\\<instanceName>;databaseName=qppdb qpp.jdbc.userName = QppMSSQLDB qpp.jdbc.password = QppPassword
Edit the [TOMCAT_HOME]/qpp/conf/PluginsContext.xml file by replacing the
11
default entry of the HSQL Dao context with the required database Dao context:
• For Oracle:
<import resource="classpath:com/quark/qpp/common/dao/rdbms/oracle/OracleDaoContext.xml"/>
• For SQL Server:
<import resource="classpath:com/quark/qpp/common/dao/rdbms/sqlserver/SqlServerDaoContext.xml"/>
Set the following global environment variables on the machine:
12
12 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
•
MAGICK_HOME : [Tomcat_Home]\qpp\ImageMagick\bin.
•
MAGICK_FILTER_MODULE_PATH : %MAGICK_HOME%/modules/filters.
•
MAGICK_CODER_MODULE_PATH : %MAGICK_HOME%/modules/coders.
Open the [TOMCAT_HOME]/conf/catalina.properties file and add the following
13
line:
Shared.Loader :${catalina.home}/qpp/conf,${catalina.home}/qpp/lib/*.jar, ${catalina.home}/qpp/publishing, ${catalina.base}/qpp/ext
Open the [TOMCAT_HOME]/conf/catalina.properties file and search for
14
org.apache.catalina.startup.TldConfig.jarsToSkip= and update:
org.apache.catalina.startup.TldConfig.jarsToSkip=a*.jar,b*.jar,c*.jar,d*.jar,e*.jar,f*.jar,g*.jar, h*.jar,i*.jar,k*.jar,l*.jar,m*.jar,n*.jar,o*.jar,p*.jar,q*.jar,r*.jar,s*.jar,t*.jar,u*.jar,v*.jar,w*.jar,x*. jar,y*.jar,z*.jar,ja*.jar,jc*.jar,jd*.jar,je*.jar,ji*.jar,jn*.jar
If Tomcat is installed with the installer:
15
Launch the Tomcat monitor. In the JAVA tab, set CATALINA_OPTS under Java Options:
• If Platform Server is running with Oracle database:
Doracle.jdbc.J2EE13Compliant=true
• For integration of LDAP (or give absolute path):
Djava.security.krb5.conf=./qpp/conf/krb5.conf
•
For Java PermGen memory space: XX:MaxPermSize=256m
If Tomcat is deployed with binaries:
16
Open the [TOMCAT_HOME]/bin/catalina.bat file and set following params:
•
JRE_HOME=C:\Program Files\Java\jdk1.7.0_76
•
JAVA_OPTS=-server -Xmx1536m -XX:MaxPermSize=128m
•
CATALINA_OPTS=-Doracle.jdbc.J2EE13Compliant=true
-Djava.security.krb5.conf=../qpp/conf/krb5.conf
Launch the Tomcat monitor. In the JAVA tab, set the following parameters:
17
•
Initial memory pool=1024 MB.
•
Maximum memory pool=1536 MB.

Server startup and verification

After you install Quark Publishing Platform Server with Tomcat and specify the port
for Quark Publishing Platform Server access, you can start Quark Publishing Platform
Server and verify your configuration. Quark Publishing Platform Server and Tomcat
are tied together. To start and stop Quark Publishing Platform Server, you need to start
and stop Tomcat.
To confirm Quark Publishing Platform Web Client access, in you browser's address field enter: http://[machineName]:[webServerPort]/workspace
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 13
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
To confirm Quark Publishing Platform Web admin access, in you browser's address field enter: http://[machineName]:[webServerPort]/admin
QuarkCopyDesk, QuarkXPress, Quark Publishing Platform Client, Quark Publishing
Platform Web Client, and Quark Publishing Platform Script Manager use the Tomcat
port to log on to Quark Publishing Platform server.

Deploying Quark Publishing Platform Server in multi-server deployment

A Quark Publishing Platform multi-server cluster is a set of Quark Publishing Platform
Server installations that has been configured to use a common database, shared asset
repository, and message queue. A multi-server cluster offers the following advantages:
• It lets you serve a larger number of requests by adding hardware.
• It lets you add active load balancing.
• It provides redundant and reliable setup.
• Failure of any specific instance in a cluster does not result in complete service outage.
Only a fraction of active sessions are affected by an instance failure, and subsequent
requests can be routed to an available active Quark Publishing Platform Server instance.
• It is transparent to clients that communicate with the load-balancing HTTP server.
To load-balance requests, you must have an HTTP serverand any HTTP load balancer
that supports the "sticky session" feature. The following HTTP servers have been tested
as load-balancing servers:
• Microsoft IIS 7 with the latest version of the IIS Tomcat connector.
• Apache 2.2 with the latest version of the JK Tomcat Connector for Apache 2.2.
• Apache 2.2 with built in mod_proxy and mod_proxy_balancer DSO modules of the
Apache 2.2.
Only requests routed through an HTTP load balancer are load-balanced among different
instances. Requests to a specific instance are always served by that instance, irrespective
of its existing load.
RMI clients must connect directly to a specific server instance.

Configuring cluster server instances or nodes

The Quark Publishing Platform Server can be deployed as a standalone server or in an
external Tomcat using the database on the initial computers, which are called nodes
of the Platform multiserver cluster. The first step in setting up cluster servers is to set
up a Quark Publishing Platform Server database for Oracle or MS SQL Server.
Platform Server deployed as a standalone server to work as nodes
On each Quark Publishing Platform Server computer:
Open the "ActiveMQ.xml" file located in the qpp/conf folder.
1
14 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
In the "ActiveMQ.xml" file, uncomment and add network connectors to integrate the
2
server instance's message queue with one or more server instances in the cluster, where
qpp-node-N is the name of a computer where another instance of Quark Publishing
Platform Server is deployed:
<networkConnectors> <networkConnector dynamicOnly="true" duplex="true" name="remote-nc" networkTTL="1000" uri="static:(tcp://qpp-node-N:61401)"/> </networkConnectors>
In the "ActiveMQ.xml" file, uncomment the transport connector(s) to integrate the
3
server instances’ message queues with the IP address and name of the server instances
in the cluster.
<<transportConnector uri="tcp://localhost:${jms.openWirePort}?wireFormat.maxInactivityDuration=0" updateClusterClients="true" rebalanceClusterClients="true" updateClusterClientsOnRemove="true" /> <transportConnector uri="tcp://10.91.32.51:${jms.openWirePort}?wireFormat.maxInactivityDuration=0"/>
Open the "web.xml" file of the workspace and admin webapps, located in the WEB-INF
4
folder for each webapp and uncomment the SessionResetFilter to handle sessions in
case of node failure.
<filter> <filter-name>SessionResetFilter</filter-name>
<filter-class>com.quark.web.security.servlet.SessionResetFilter</filter-class>
<init-param> <param-name>jvmRoute</param-name> <param-value>qpp1</param-value> </init-param> <init-param> <param-name>sessionCookieName</param-name> <param-value>JSESSIONID</param-value> </init-param> <init-param> <param-name>sessionInitUrls</param-name> <param-value> /workspace/reconnectUser.qsp /workspace/login.qsp </param-value> </init-param> </filter> <filter-mapping> <filter-name>SessionResetFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
In the "ServerApp.properties" file located in the [QPP Server]/conf folder, assign a
5
unique value to server.id.prefix, identifying the server instance.
In the "AssetServiceContext.xml" file found in
6
{install_path}/Server/lib/qpp-core-{version}.jar, uncomment the
PersistantLockedAssetsRegistry and comment the LockedAssetsRegistryImpl beans.
<!-­ <bean id="lockedAssetsRegistry" class="com.quark.qpp.core.asset.service.impl.LockedAssetsRegistryImpl"> <property name="assetMessagePublisher" ref="assetMessagePublisher"/> </bean>
-->
<bean id="lockedAssetsRegistry" class="com.quark.qpp.core.asset.service.impl.PersistantLockedAssetsRegistry">
<property name="assetMessagePublisher" ref="assetMessagePublisher"/> <property name="lockedAssetsDao" ref="lockedAssetsDao"/> </bean>
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 15
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
In the "server.xml" file located in the [server-path]/conf folder, assign a unique
7
value to the jvmRoute attribute of the <Engine> tag.
<Engine name="Catalina" defaultHost="localhost" jvmRoute="node1">
Rename the "serviceArchivesMultiServer" folder, located at
8
{TOMCAT_HOME}/webapps/webServices/WEB-INF, to "services".
Repeat the above steps for all Quark Publishing Platform nodes.
Platform Server deployed in external Tomcat
On each Quark Publishing Platform Server computer:
Deploy a standalone instance of Quark Publishing Platform Server in external Tomcat,
1
using the database on the initial computer.
Open the "ActiveMQ.xml" file located in the qpp/conf folder and add network
2
connectors to integrate the server instance's message queue with one or more server instances in the cluster, where qpp-node-N is the name of a computer where another
instance of Quark Publishing Platform Server is deployed:
<networkConnectors> <networkConnector dynamicOnly="true" duplex="true" name="remote-nc" networkTTL="1000" uri="static:(tcp://qpp-node-N:61401)"/> </networkConnectors>
Uncomment the transport connector(s) in the "ActiveMQ.xml" file to integrate the
3
server instances’ message queues with the IP address and name of the server instances
in the cluster.
<<transportConnector uri="tcp://localhost:${jms.openWirePort}?wireFormat.maxInactivityDuration=0" updateClusterClients="true" rebalanceClusterClients="true" updateClusterClientsOnRemove="true" /> <transportConnector uri="tcp://10.91.32.51:${jms.openWirePort}?wireFormat.maxInactivityDuration=0"/>
In the "ServerApp.properties" file located in the [QPP Server]/conf folder, assign a
4
unique value to server.id.prefix, identifying the server instance.
In the "server.xml" file located in the [server-path]/conf folder, assign a unique
5
value to the jvmRoute attribute of the <Engine> tag.
<Engine name="Catalina" defaultHost="localhost" jvmRoute="node1">
Edit the tomcat_home/conf/context.xml file as follows:
6
<Context sessionCookiePath="/">
Rename the "serviceArchivesMultiServer" folder, located at
7
{TOMCAT_HOME}/webapps/webServices/WEB-INF, to "services".
Repeat the above steps for all Quark Publishing Platform nodes.
8

Configuring IIS as an HTTP load balancer

To configure IIS 7 as an HTTP load balancer:
The first step is to deploy the Tomcat connector. For more details on how to do this,
1
see http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html. Create a new folder
16 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
named "TomcatConnector," then put the "isapi_redirect.dll" file from the Tomcat
Connector for IIS build.
Create a new file named "isapi_redirect.properties" in the same folder, and insert the
2
following into the file:
extension_uri=/jakarta/isapi_redirect.dll log_file=C:\TomcatConnector\Log\isapi.log # Make sure the directory listed for log files in the # "isapi_redirect.properties" file exists log_level=info worker_file=C:\TomcatConnector\worker.properties worker_mount_file=C:\TomcatConnector\uriworker.properties
Create a new file named "workers.properties" in the same folder, and insert the following
3
into the file, where qpp-node1 and qpp-node2 are the values of the jvmRoute attribute
as specified in the "server.xml" file for each Quark Publishing Platform Server:
worker.list=TomcatBalancer worker.TomcatBalancer.type=lb worker.TomcatBalancer.balance_workers=qpp-node1,qpp-node2 worker.TomcatBalancer.sticky_session=True worker.TomcatBalancer.sticky_session_force=True worker.TomcatBalancer.method=Request worker.TomcatBalancer.lock=Pessimistic
worker.qpp-node1.type=ajp13 worker.qpp-node1.host=qpp-node1
# This should be the same as the port in the AJP connector defined # in the "server.xml" file for the Tomcat server in which Quark # Publishing Platflrm is deployed worker.qpp-node1.port=61398
worker.qpp-node1.lbfactor=3
worker.qpp-node2.type=ajp13 worker.qpp-node2.host=qpp-node2
# This should be the same as the port in the AJP connector defined # in the "server.xml" file for the Tomcat server in which Quark # Publishing Platflrm is deployed worker.qpp-node2.port=61398
worker.qpp-node2.lbfactor=3
Create a new file named "uriworker.properties" in the same folder, and insert the
4
following into the file:
/admin/*=TomcatBalancer /admin=TomcatBalancer /workspace/*=TomcatBalancer /workspace=TomcatBalancer /webservices/*=TomcatBalancer /webservices=TomcatBalancer /rest/*=TomcatBalancer /rest=TomcatBalancer /messaging/*=TomcatBalancer /messaging=TomcatBalancer /qxpsmadmin/*=TomcatBalancer /qxpsmadmin=TomcatBalancer /favicon.ico=TomcatBalancer /*=TomcatBalancer /qxpsm/*=TomcatBalancer /qxpsm=TomcatBalancer
This file contains the mappings of the URLs that need to be handled by IIS and
forwarded to Quark Publishing Platform Servers.
Using the IIS management console, add a new virtual directory named "jakarta" to
5
your IIS Web site, with the physical path of the directory where you placed the
"isapi_redirect.dll" file.
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 17
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
Give the virtual directory execute permission. Select the virtual folder, double-click
6
Handler Mappings, and then click Edit Feature Permissions in the Actions pane.
Check Execute in the Edit Feature Permissions dialog box, and then click OK.
Add an ISAPI filter to the IIS Web site. Select the Web site, double-click ISAPI Filters,
7
and then click Add in the Actions pane. In the Add ISAPI Filter dialog box, enter a
name and the path of the "isapi_redirect.dll" file, and then click OK.
Configure the ISAPI and CGI Restrictions feature. Navigate to the Server Home screen,
8
double-click ISAPI and CGI Restrictions, and then click Add in the Actions pane. In
the Add ISAPI or CGI Restriction dialog box, enter a name and the path of the
"isapi_redirect.dll" file, check Allow extension path to execute, and then click OK.
Enable Windows authentication. Navigate to your Web site and double-click
9
Authentication. Right-click Windows Authentication and choose Enable, disable
the other authentication options, and then restart IIS.
To verify the installations, start Quark Publishing Platform Server on all nodes, then
10
access each server using the computer name or IP address and port of the IIS server.
The IIS server should serve and load-balance the request using the Tomcat connector.
You can view the details in the log file identified in the "isapi_redirect.properties" file.

Configuring Apache Web Server as an HTTP load balancer

To configure Apache Web Server 2.2 with the latest version of the JK Tomcat Connector
for Apache 2.2 as an HTTP load balancer:
The first step is to deploy the Tomcat connector. For more details on how to do this,
1
see http://tomcat.apache.org/connectors-doc/miscellaneous/faq.html. Copy the "mod_jk.so"
file from the Tomcat Connector download location to
{Apache_2.2_installation}/modules.
Open the file {Apache_2.2_installation}/conf/httpd.conf in a text editor and
2
insert the following content:
LoadModule jk_module modules/mod_jk.so <IfModule jk_module>
JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogStampFormat "[%H:%M:%S] " JkRequestLogFormat "%T" JkLogLevel error JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories <Directory /> AllowOverride All <Limit GET HEAD POST PUT DELETE OPTIONS> Order Allow,Deny Allow from all </Limit> </Directory> JkMount /workspace TomcatBalancer JkMount /workspace/* TomcatBalancer JkMount /webservices TomcatBalancer JkMount /webservices/* TomcatBalancer JkMount /admin TomcatBalancer JkMount /admin/* TomcatBalancer JkMount /rest TomcatBalancer JkMount /rest/* TomcatBalancer JkMount /messaging TomcatBalancer JkMount /messaging/* TomcatBalancer JkMount /qxpsm TomcatBalancer JkMount /qxpsm/* TomcatBalancer JkMount /qxpsmadmin TomcatBalancer JkMount /qxpsmadmin/* TomcatBalancer </IfModule>
18 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
Create a file named {Apache_2.2_installation}/conf/workers.properties
3
and add the following content to it, where qpp-node1 and qpp-node2 are the values of the jvmRoute attribute as specified in the "server.xml" file for each Quark Publishing
Platform Server:
worker.list=TomcatBalancer
worker.TomcatBalancer.type=lb worker.TomcatBalancer.balance_workers=qpp-node1, qpp-node2 worker.TomcatBalancer.sticky_session=True
# This should be commented out, if it is not, you cannot connect to the Apache Web server which # acts as the load balancer. worker.TomcatBalancer.sticky_session_force=True
worker.TomcatBalancer.method=Request worker.TomcatBalancer.lock=Pessimistic
worker.qpp-node1.type=ajp13
# This should be the IP address of the first QPP node worker.qpp-node1.host=Server 1
# 8009 is for external tomcat server # 61398 is for embedded tomcat with QPP worker.qpp-node1.port=61398
worker.qpp-node1.lbfactor=3
worker.qpp-node2.type=ajp13
# This should be the IP address of the first QPP node worker.qpp-node2.host=Server 2
# 8009 is for external tomcat server # 61398 is for embedded tomcat with QPP worker.qpp-node2.port=61398
worker.qpp-node2.lbfactor=3
Restart Apache 2.2 httpd.
4
To verify the installations, start Quark Publishing Platform Server on all nodes, then
5
access each server using the computer name or IP address and port of the Apache
server. The Apache server should serve and load-balance the request using the Tomcat
connector. You can view the details in the log files at
{Apache_2.2_Installation}/logs.

Configuring server caches flushing mechanism

Platform Server provides two mechanisms to flush caches across all server instances
in case of an update:
• Notification based - This mechanism clears the cache asynchronously. The Notification
based cache flushing is accomplished by publishing of a message of type CACHE with property FLUSH_INTERCEPTOR. This is the default configured mechanism.
• REST request based - This mechanism clears the cache synchronously. The REST based
mechanism makes an HTTP request to every peer node to trigger its cache flushing:
http://{peerNode}:61400/rest/service/xcache/flush/{interceptorName}.
This mechanism is not the default configuration, but you may configure it if needed.
In order to configure REST based cache flushing mechanism, make the following
changes:
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 19
DEPLOYING QUARK PUBLISHING PLATFORM SERVER TO EXTERNAL SERVER CONTAINERS
Open the "CacheManager.xml" file found in
1
{install_path}/Server/lib/qpp-server-common-{version}.jar
Comment the asyncRemoteMessenger and uncomment the
2
synchronousRemoteInvoker. Inject this bean instead of asyncRemoteMessenger in
baseCacheFlushingInterceptor.
<!-- Uncomment and inject this bean instead of asyncRemoteFlushingMessenger in baseCacheFlushingInterceptor for synchronous REST based cache invalidation. --> <bean id="synchronousRemoteInvoker" class="com.quark.qpp.common.caching.SynchronousRemoteInvoker" > <property name="remoteHosts" value="${server.peer.url}"/> <property name="httpContext" value="${server.cache.remoteFlush.context}"/> </bean> <bean class="com.quark.qpp.common.caching.RemoteFlushController"> <property name="flushingInterceptorMap" ref="flushingInterceptorMap"/> </bean>
<!-- <bean id="asyncRemoteMessenger" class="com.quark.qpp.core.messaging.service.impl.AsyncRemoteMessenger" > <property name="messagePublisher" ref="messagePublisher"/> </bean> -->
Save and close the file.
3
Restart the server.
4
In the "ServerApp.properties" file located in the [QPP Server]/conf folder,
5
uncomment the following:
# Uncomment following properties to configure QPP cluster with synchronous cache update # Set comma separate URIs of peer server instances which are part of Cluster
server.peer.url=http://{peerHostN 1}:61400,http://{peerHostN 2}:61400
# Http context which may be used to invoke cache flushing server.cache.remoteFlush.context=rest/service/xcache/flush
20 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE

ENABLING SECURE SOCKETS LAYER (SSL) FOR QUARK PUBLISHING PLATFORM SERVER

Enabling Secure Sockets Layer (SSL) for Quark Publishing Platform Server
You can configure Quark Publishing Platform with different security options. In
addition to your own network security specifications, you can specify SSL protocol for
your Quark Publishing Platform client applications.

SSL support

You can configure your application server containers and all Quark Publishing Platform
clients to run in secure mode with SSL technology. This section explains the
configuration process.
It is also possible to run Quark Publishing Platform without embedding Tomcat in
JVM. See "Deploying in external Tomcat" for information about setting up Quark
Publishing Platform without embedding Tomcat.
To manage Web applications in the Quark Publishing Platform environment, Quark
Publishing Platform Server embeds an instance of Apache Tomcat 7.0.61 in its JVM.
The four Web applications in Quark Publishing Platform include Quark Publishing
Platform Web Client, Quark Publishing Platform Console, Quark Publishing Platform
Renderer Manager, and Quark Publishing Platform Web Services.
When you enable SSL, it applies to all Quark Publishing Platform client applications
deployed in Quark Publishing Platform Server.

Enabling SSL in Quark Publishing Platform Server

The instructions below address two scenarios. The "server.xml" file you edit contains
XML tags for both scenarios, which you need to enable or disable by "commenting"
and "uncommenting" specific tags.
To enable SSL for secure HTTP for all Quark Publishing Platform Web applications:
Open the "server.xml" file located in the {install_path}/conf folder.
1
Comment the following tag:
2
<Connector port="61400" maxHttpHeaderSize="8192"maxThreads="150" minSpareThreads="25" maxSpareThreads="75"enableLookups="false" redirectPort="61399" acceptCount="100"connectionTimeout="20000" disableUploadTimeout="true" />
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 21
ENABLING SECURE SOCKETS LAYER (SSL) FOR QUARK PUBLISHING PLATFORM SERVER
Uncomment the following tag:
3
<Connector port="61399" maxHttpHeaderSize="8192"MaxThreads="150" minSpareThreads="25" maxSpareThreads="75"enableLookups="false" disableUploadTimeout="true"acceptCount="100" scheme="https" secure="true"clientAuth="false" sslProtocol="TLS" />
Replace 61399 with 61400 (or any port on which Tomcat will be listening for secure
4
connections).
Save and close "server.xml."
5
On Quark Publishing Platform Server machine, open the command prompt and execute
6
the follwoing command:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
Provide the details in the prompts. Password should be changeit.
7
Restart the Quark Publishing Platform Server.
8
Access the Admin webpage: https://servername:61399/admin
9
This configuration creates one keystore with a private and public key pair. This is a
self sign certificate.
For more information on SSL configuration, including the use of a Certificate Authority,
10
please see the Apache Tomcat SSL information here:
url:https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html
This change means Quark Publishing Platform client applications can use HTTPS. For
example, the URL for a Quark Publishing Platform Web Client user would be as follows:
https://[server name]:61399/workspace.

Configuring Platform clients to log on to an SSL enabled Server

Mac OS X QuarkXPress and QuarkCopyDesk users must fetch a SSL certificate from
Quark Publishing Platform Server before they can log on. To do so, each user should
launch Terminal and run the following command, substituting the IP address of the Quark Publishing Platform Server computer for [server name]:
echo | openssl s_client -connect [server name]:443 > [server name].pem
This command retrieves a copy of the server certificate named "[server name].pem". Put this file in the ~/Library/Application Support/Quark/QPP/Certificates folder (or, if you have customized the plist file at ~/Library/Application
Support/Quark/QPP/[QPP Framework Version], put the file there).
If the "Quark Publishing Platform" and "Certificates" folders do not already exist at the
above locations, create them there manually.
Quark Publishing Platform clients running on Windows do not require a server-based
SSL certificate.
22 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
ENABLING SECURE SOCKETS LAYER (SSL) FOR QUARK PUBLISHING PLATFORM SERVER

Verifying and using SSL

To verify and use SSL:
Start the Quark Publishing Platform Server.
1
Test Quark Publishing Platform Web Client access by entering the following:
2
https://[machine IP/name]:61399/workspace.
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 23

QUARK PUBLISHING PLATFORM SERVER — MANUAL CONFIGURATION

Quark Publishing Platform Server — Manual configuration
You can change the default configuration after you install Quark Publishing Platform
Server. In addition to setting parameters with JConsole while Quark Publishing Platform
Server is running, you can adjust settings in different .xml files and .properties files.
You can also adjust memory allocation for your JVM configuration.

Editing "ServerApp.properties"

To edit "ServerApp.properties":
Open the "ServerApp.properties" file in the [QPP Server]/conf folder.
1
Set the rmi.port value to the number of the port on which the RMI registry listens.
2
Java-based RMI clients such as ScriptManager connect through this port.
Set the rmi.servicePort value to the port number used by the RMI server where
3
Quark Publishing Platform service objects are registered.
Set the namingservice.port value to the port number used for listening to object
4
resolution requests by the CORBA naming service.
Set the serverORB.port value to the port number used by the ORB where Quark
5
Publishing Platform service objects are activated.
Set the jms.openWirePort value to the port number opened for JMS communication
6
via the OpenWire protocol. Java clients such as Quark Publishing Platform Script
Manager connect to this port to listen to server notifications.
Set the webServer.port value to the port number on which Tomcat listens for HTTP
7
connections. Quark Publishing Platform Web Client and SOAP clients connect through
this port. The value should be set to that specified for the HTTP connector in the
Tomcat "server.xml" file.
Set the socketStreaming.port value to the port number to be used for file transfer
8
(upload/download).
To bind Quark Publishing Platform Server to a particular IP address, set the
9
server.machinename value to that IP address and set server.bindtoip=true. Or,
if you have multiple network cards and you want to bind Quark Publishing Platform to all of their IP addresses, set server.machinename=localhost,
24 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
QUARK PUBLISHING PLATFORM SERVER — MANUAL CONFIGURATION
server.bindtoip=false, and server.addtionalnames=[non-default-ip1],[non-default-ip2].
Set the server.additionalnames value to specify the global IP address where the
10
firewall is exposed.
Enter the webServer.port value you configured for Tomcat (8080, for example).
11
To allow users to log on to Quark Publishing Platform Server even when the directory
12
server is not running, set authentication.external.cacheTicket = true.
To set the password case sensitivity, set the server.password.case.sensitive
13
value to false if case sensitivity is not considered for comparing passwords. This option
is not valid if using LDAP for external authentication.
To configure a session TimeOut, set the session.maxIdle value to specify the session
14
timeout in seconds. and set the session.eviction.thread.delay value to specify
the frequency of the session eviction thread in seconds.
The Repository status updater is the background thread that runs at a specified
15
frequency to test whether the underlying repository is active or not and to update the
status of the same in server database. To configure the repository status updater's sleep interval, set the repository.status.updator.sleepInterval value to specify
the interval in seconds after which the repository status update thread should run.
If the Realm verif. For Admin. Requests is set in QuarkXPress Server, the
16
username and password for QuarkXPress Server need to be set in this file. Set the
following properties to configure the QuarkXPress Server:
•
Set the qxps.username value to specify the QuarkXPress Server username.
•
Set the qxps.password value to specify the QuarkXPress Server password.
•
Set the qxps.locale value to specify the location of QuarkXPress Server.

Editing "PublishingPool.properties"

To edit "PublishingPool.properties":
Open the "PublishingPool.properties" file in the Server Installation conf folder.
1
Set the publishingThread.pool.maxActive value to specify the maximum number
2
of background publishing threads that can run simultaneously.
Set the publishingThread.pool.maxIdle value to specify the maximum number
3
of idle threads in the pool.
Set the publishingThread.pool.minIdle value to specify the minimum number
4
of idle threads in the pool.
Set the publishingThread.pool.maxWait value to specify the time in milliseconds
5
that the publishing request should wait while borrowing a thread from the pool.
Set the publishingThread.pool.minEvictableIdleTimeMillis value to specify
6
the time in milliseconds for a thread to be in the pool before it can be evicted.
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 25
QUARK PUBLISHING PLATFORM SERVER — MANUAL CONFIGURATION
Set the publishingThread.pool.timeBetweenEvictionRunsMillis value to
7
specify the time in milliseconds after which the evictor thread should run to remove
idle threads.

Configuring Quark Publishing Platform Renderer for Quark Publishing Platform usage

To configure Quark Publishing Platform Renderer for Quark Publishing Platform usage:
Open the QXPSM Admin Client by navigating to the following URL in a Web browser:
1
http://[QPP server name]:[port]/qxpsmadmin.
In the Manage Servers pane, click Add Servers and add the Quark Publishing Platform
2
instance of Quark Publishing Platform Renderer. For more information, see A Guide
to Quark Publishing Platform Renderer.

Editing "Qla.properties"

To edit "Qla.properties":
Open the "Qla.properties" file in the [QPP Server]/conf folder.
1
Enter the IP address or hostname of the QLA Server in the QlaServer.machinename=
2
field.
Enter the port number of the QLA Server in the QlaServer.port= field.
3
If you have a backup QLA server, enter the IP address (or hostname) and port number
4
in the Backup.QlaServer.machinename= and Backup.QlaServer.port= fields.
Enter the Quark Publishing Platform serial number in the Qla.SerialNumber= field.
5
The QLA Server Console and QLA Client applications display your Quark Publishing
Platform serial number.
Save and close "Qla.properties."
6

Extended configuration files

Configuration files are split into base and ext for ease of deployment.
User specific custom beans, processes and publishingchannels should be defined in .ext files in the Server Installation ext folder, to separate custom extensions and
maintain them after a software upgrade.
• ChannelConfig-ext.xml
• content-mimetype-mappings-ext.xml
• custom-xml-types-ext.xml
• IndexingChannels-ext.xml
• PluginsContext-ext.xml
26 | QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE
QUARK PUBLISHING PLATFORM SERVER — MANUAL CONFIGURATION
• ProcessConfig-ext.xml
• PublishingConfig-ext.xml
Configuring Platform Server to be used for publishing with Quark XML Author ­Sharepoint Adapter
To configure Quark Publishing Platform Server to be used for publishing with Quark
XML Author - Sharepoint Adapter:
Open the "sharepoint.properties" file in the [QPP Server]/publishing folder.
1
Set the sharepoint.username value to be the login name of a user with access to
2
Sharepoint sites.
Set the sharepoint.userpassword value to be the login password of the user specified
3
above.
Set the sharepoint.userdomain value to be the domain of the user specified above.
4
Set the sharepoint.sitecollection value to be the URL of a Sharepoint Site
5
Collection which contains documents required during publishing.
Restart the Server.
6
Configuring Platform Server to be used for publishing with Quark XML Author ­FileNet Adapter
To configure Quark Publishing Platform Server to be used for publishing with Quark
XML Author - FileNet Adapter:
Open the "contentengine.properties" file in the [QPP Server]/publishing folder.
1
Set the filenet.stanza value to be the stanza for filenet content engine connection.
2
You need to edit the parameter only when the filenet server is configured to use a
stanza other than FileNet.
Set the filenet.username value to be the FileNet username.
3
Set the filenet.userpassword value to be the value to be the FileNet password of
4
the user specified above.
Set the filenet.connectionuri value to be the Connection URI of the FileNet
5
Content Engine WebService.
Restart the Server.
6

JVM memory allocation on Windows

On Windows, you can specify JVM memory allocation in different locations, depending
on how you start Quark Publishing Platform Server. On 64-bit operating systems, you
QUARK PUBLISHING PLATFORM 2015 SYSTEM ADMINISTRATION GUIDE | 27
Loading...
+ 61 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use