Home Blog Enterprise 2.0: Deploying Publisher in Production
󰀄

There is a major change that you need to make to the configuration of Publisher before deploying it into production and it is a change that is overlooked in a lot of ALUI deployments. When you install Publisher, it is not set up to use as much memory as a production instance of Publisher should use. Making this change is easy though, as the recommended configuration settings are actually in the config files, but are commented out. In order to make the change, open up the service.conf file in the ptcs/6.x/settings/config directory and find the following section:

Comment out the lines preceding this section dealing with java parameters and memory usage and then uncomment this section. Restart your publisher service and you are set for production! Check your publisher diagnostic page to make sure that the memory settings took…

One Trackback

  1. [...] in point:  configuring the memory parameters for Collaboration Server.  While Publisher utilizes a config file for memory settings, Collaboration Server passes memory parameters via the service startup path.  So, if you’ve [...]

Comments

Write a comment:

*

Your email address will not be published.

󰁓
󰀰 󰀩 󰀭 󰀎