Deploying your configuration changes

To deploy your configuration changes to an actual production server, you must build a .war or .ear file and deploy it on the application server. By design, you cannot directly deploy configuration files from Studio to a production application server.

Because the bundled QuickStart development server and Studio share the same configuration directory, you do not need to deploy your configuration changes to the QuickStart development server.

Hot-deploy PCF files

About this task

Editing and saving PCF files in the Page Configuration (PCF) editor does not automatically reload them in the QuickStart server, even if there is a connection between it and Studio. You do not actually need to be connected to the server from Studio to reload PCF files.

You can also use this method to reload display keys.

Procedure

  1. Navigate to the PolicyCenter web interface on the deployment server, and log in.
  2. Reload the PCF configuration using either the Internal Tools page or the Alt+Shift+L shortcut.

Hot-deploy Gosu files

About this task

Editing and saving Gosu files in Studio does not automatically reload them in the QuickStart server, even if there is a connection between it and Studio. To reload the Gosu files, do one of the following:

Procedure

  • To recompile all files, click Build > Compile.
  • To compile only files that were changed since the last compile, click Build > Make Project.