Create And Edit a Rendering Profile

Rendering profiles depend on the applications that perform the rendering. If only one Meridian Enterprise Server server is deployed, the system is simple and all rendering applications must be installed on the same computer. But when a cluster is deployed, the system can be more complex. For a list of the rendering application versions that are compatible with your version of Meridian Enterprise, see Publisher Rendering Applications.

For example, the primary node might be dedicated to the non-rendering tasks and dedicated nodes deployed to perform the compute-intensive rendering tasks. All publishing jobs must be defined on the primary node where the rendering applications are not installed. Some of the publishing job options require information from the computer where the rendering applications are installed. Moreover, a publishing job that performs rendering should only be able to be assigned to and run on the node where the rendering application is installed.

Meridian Enterprise Server meets these challenges with the ability to scan the cluster nodes for the rendering applications that are installed on them. The information is cached on the primary node for instant access. The system uses this information to guide you in creating only rendering profiles for which the rendering applications are installed and only assigning jobs to the correct nodes. You should start a scan when new rendering applications are installed or custom paper sizes are created on the node.

To create or edit a rendering profile:

1. In Meridian Enterprise Server Administration Console, in the Data Exchange group, click Rendering Profiles.

   The All Rendering Profiles page appears and lists the existing profiles grouped by the name of the computer (cluster node) to which they are assigned.

   If cached rendering application information exists, the message Native application capabilities found in cluster machines is shown at the bottom of the page. The nodes are listed on the right side of the page with information about when the node was last scanned.

2. If no rendering applications are cached or if new applications have been installed since the last scan, scan the cluster for rendering application changes before proceeding:

   • On the right side of the page, next to the name of the node that you want to scan, click Scan.

     The node is scanned and the information is cached. For scanning to work when using SQL Server, the Publisher nodes need to have the SQL driver installed, and they need to be able to connect to the SQL Server configuration database.

3. Choose one or more of the following options:

   • To create a new rendering profile:

     1. Click New.

        The New Rendering Profile dialog box appears and lists the available rendering modules for selection.

     2. Select a rendering module.

     3. Click Next.

        The name page appears.

     4. Accept the default name or type a more descriptive name for the rendering profile in the Name box.

     5. Click Next.

        A page with the particular options for the rendering module that you selected appears.

   • To edit an existing rendering profile:

     • Select the profile that you want to edit, and then in the toolbar, click Properties.

       A page with the particular options for the rendering module that you selected appears.

     • Double-click the profile that you want to edit.

       A page with the particular options for the rendering module that you selected appears.

4. Configure the particular options for the rendering module that you selected as described in the following topics.

5. Click Save.