Skip to content
CA Service Management - 17.1
Documentation powered by DocOps

How to Modify the Web Interface using Web Screen Painter

Last update January 18, 2017

Web Screen Painter (WSP) lets you modify web forms to the requirements of your site without programming.

Some of the Knowledge Management forms cannot be modified in the design view of WSP. For these forms, there are alternate approaches to providing the customization, such as:

  • Document view -- the document template that is used when creating the document determines the contents of this page. These templates can be modified on the administration tab under documents, document templates.
  • Knowledge categories document list -- you can modify this page by using WSP, but it is also managed by user preferences. The “preferences” screen provides personalization per user for defining which document properties display in the document list and how many documents display per page.

Follow these steps:

  1. Verify the Prerequisites
  2. " class="conf-macro output-inline" data-hasbody="true" data-macro-name="sp-plaintextbody-link">Start WSP
  3. Choose the Form to Modify
  4. Modify a Form
    WSP always saves changes on the server where WSP is installed. When you save a file, it becomes accessible to other WSP users in a preview session, but it is invisible to typical CA SDM users. This is because WSP saves all files in the site/mods/wsp directory, and this directory is not used by a typical CA SDM session.
  5. If you are making web form changes in the test system, Migrate from Test to Production System.
  6. Publish Form Changes.
  7. (If necessary) Delete Forms After Publishing.

Verify the Prerequisites

Verify the following prerequisites before you begin the customization:

  • Modified the schema that you want to add in the web forms.
  • (For advanced availability configuration only) Verified that the following prerequisites to publish the web forms successfully:
    • (Recommended) CA SDM services are up and running on all the CA SDM servers. Otherwise WSP publishes only on the CA SDM servers that are up and running.
    • (Required) At least one webengine instance running on every CA SDM server.

Start WSP

Start WSP to modify web forms.

Follow these steps:

  1. Log in to the computer where you have WSP installed.
  2. Start WSP.
    • (Windows) Click Start, Programs, CA, Service Desk, WSP.
    • (UNIX) Enter the command pdm_wsp with $NX_ROOT/bin in your path.

      Important! When you use UNIX, ensure that you have Firefox that is installed to use WSP.
    The WSP login window opens.
  3. Enter your credentials.
    WSP displays the main form.

Select the Form to Modify

You can create a form or can open an existing form to modify. Select from the following possibilities:

Create a Form

Create a form in WSP.

Follow these steps:

  1. Click File, New.
    The New Form dialog opens.
  2. Complete the following fields, as appropriate:
    • Interface or File Type
      Indicates the file type of the form. For example, to create an HTMPL form select an interface (Analyst, Customer, Employee, Default, or PDA). To create a form of other file type by select the type directly (CSS style sheet, HTML, or JavaScript). When you select an interface or file type, WSP displays a list of all available templates for the selected file type in the File Name field.
    • Form Group
      Indicates the form group (as defined for your CA SDM installation) where you want to create your new form or file. If you have not defined any form groups, only the DEFAULT form group is listed.
    • File Name
      Indicates the template for the selected interface or file type. A template contains the basic requirements for a new form or file of the desired type.
    • Select table for new list or detail form
      Indicates the CA SDM tables for which you can create a new list or detail form. This field is populated according to your selection of an interface (Analyst, Customer, Employee, Default, or PDA).

      Note: Only one detail or list form can exist for each table in a forms group, so edit an existing form (rather than create one) for tables that already have an existing form. If you want to have multiple versions of a form, create one or more form groups to hold the additional versions.
  3. Click New.
  4. The form is displayed for your customizations. The following two tabs are displayed:
    1. Design
      Available for detail forms, list forms, and menu bar forms, and shows the controls on the form that is laid out more or less as a user would see them. It is not an image of how the form looks to an end user. To see this, select Tools, Preview.
    2. Source
      A Notepad-style editor allowing you to review and edit the source code for a form. Some forms are editable only in the Source tab. For those forms, the edit window opens up on the Source tab, and the Design tab is disabled.

    The form is ready for customization.

    Important! When you create or edit a detail or list form, use the list_ and detail_ prefixes to name the HTMPL file. For example, use list_test.htmp" and detail_test.htmpl. This prefix lets you correctly preview a form. When you save a detail template with a custom name, you must also manually edit the <PDM_WSP> tag. For example, <PDM_WSP mode=edit preview="test.htmpl+OP=CREATE_NEW" factory=cr>.

Open an Existing Form

Open an existing form in WSP to modify it.

Follow these steps:

  1. Select File, Open.
    The Open Form dialog opens.
  2. Select the Interface (Analyst, Customer, Employee, Default) or File Type (CSS style sheet, JavaScript, or HTML) and the forms group that contains the form you want to edit.
  3. Select either the form you want from the list, or enter its name in the textbox.
    When you enter a name in the text box, WSP automatically scrolls the list to the first name matching the characters entered. You can use the Files of Status drop-down list to restrict the list of files displayed:
    • Site Modified with Unpublished Changes (+)
      Restricts the list to files that have been modified with WSP, but not yet published. These files are identified with a plus sign (+) after the file name.
    • Site Modified (*)
      Restricts the list to forms modified at your site, both published and unpublished. The unpublished files are identified with a plus sign (+) after the file name. The published site modifications are identified with an asterisk (*) after the file name.
    • All
      Displays the list with no restrictions. The unpublished files are identified with a plus sign (+) after the file name. The published site modifications are identified with an asterisk (*) after the file name.
  4. Click Open.
    The form is displayed and ready for your customization.

Modify a Form

After you open the form you want to edit in WSP, you can use the toolbar, menu commands, and shortcuts to customize it. You can perform the following customization:

  • Insert a Control
  • Edit Control Properties
  • Modify Menu Bars
  • Modify style sheets
  • Modify Mouse-Over Preview Form
  • Modify Data Grid List on List Form
  • Modify Notebooks on Detail Form
  • Modify HTML and JavaScript Files

Insert a Control

Add a control on the form. For example, add a textbox in the form.

The controls that can be inserted on both list and detail forms are the following:

Control Icon Description
Insert Row BSVC_r12.1--Inserting a Control Causes the selected control to be the last in its current row (moves following controls to the next row).
Delete Row N/A Deletes all controls on the same row as the currently selected control.
Text box BSVC_r12.1--Inserting a Control (2) Inserts a single or multi-line text box for editing a string or text field.
Dropdown BSVC_r12.1--Inserting a Control (3) Inserts a drop-down list for editing a field validated against a table.
Lookup BSVC_r12.1--Inserting a Control (4) Inserts a lookup control for editing a field validated against a table. The control consists of a text box with a hyperlink in the label that pops up a select form.
Button BSVC_r12.1--Inserting a Control (12) Inserts a button.
Hierarchical Lookup BSVC_r12.1--Inserting a Control (5) Similar to a Lookup control, except that it is used for a field with a hierarchical selector (such as request category).
Date BSVC_r12.1--Inserting a Control (6) Inserts a date field. The control consists of a text box with a hyperlink in the label that pops up a date selector.

The following additional controls are available for detail forms only:

Control Icon Description
Checkbox BSVC_r12.1--Inserting a Control (7) Inserts a check box.
HTML Editor BSVC_r12.1--Inserting a Control (8) Inserts an HTML editor for a text field that contains HTML.
Read Only text box BSVC_r12.1--Inserting a Control (9) Inserts a non-editable text field.
Read Only Lookup BSVC_r12.1--Inserting a Control (10) Inserts a non-editable lookup field. The field is displayed as a hyperlink to pop up the detail form defining it.
Read Only BSVC_r12.1--Inserting a Control (11) Inserts a non-editable date field.
Notebook BSVC_r12.1--Inserting a Control (13) Inserts a notebook. There can only be one notebook on a detail form, so this control can be inserted only on forms that do not already contain a notebook.

The following additional control is available for list forms only:

Control Icon Description
List BSVC_r12.1--Inserting a Control (14) Inserts a list. There can only be one list on a list form, so this control can only be inserted on new list forms.

Follow these steps:

  1. Right-click the form at the location where you wish to add the control and select Insert Control.
    A drop-down list is displayed.
  2. Select the insert control dialog options.
    The control is placed on the form.
  3. Select Tools, Preview to check how the form is displayed to the end user. Although it resembles a standard CA SDM window, and most buttons and menus are functional, it is not a standard session, and you should not attempt to use it that way.
  4. Click File, Save.
    The controls are added on a form.

Insert Control Dialog Options

Open the Insert Control dialog from the File menu. The dialog lists all the appropriate UI controls for the section of the form you select to edit.

The dialog contains the following options:

  • Insert Before
    Inserts the selected control from the list before the currently selected control on the base form, and makes it the currently selected control.
  • Insert After
    Inserts the selected control from the list after the currently selected control on the base form, and makes it the currently selected control.
  • Prev
    Moves the currently selected control to the control that precedes it on the form.
  • Next
    Moves the currently selected control to the control that follows it on the form.
  • Properties
    Opens the Properties dialog for the currently selected control.
  • Close
    Closes the Insert Control form.
  • Close Form After Insert
    (Enabled) Inserts the selected control and closes the Insert Control dialog when you click Insert Before or Insert After.
    (Disabled) Inserts the selected control when you click Insert Before or Insert After. The Insert Control dialog remains open to insert additional controls or request properties for the currently selected control. After you clear the check box, the Close Form After Insert check box remains unchecked until you either select it again or end your WSP session.
    Default: Enabled

Edit Controls Properties

Edit the properties of a control.

Follow these steps:

  1. Select the control and press F4.
    The Properties dialog opens.
  2. Change properties as appropriate. For example, the Caption property specifies the header label that is displayed above a control. To specify this property, enter the desired value in the cell to the right of the Caption property.
  3. Close the Properties dialog.
  4. Select Tools, Preview to check how the form is displayed to the end user. Although it resembles a standard CA SDM window, and most buttons and menus are functional, it is not a standard session, and you should not attempt to use it that way.
  5. Click File, Save.
    The properties of the control are modified and the form is saved.

Modify Menu Bars

Forms with names beginning menubar_ define a menu bar. The Design view for a menu bar displays the menu at the top. You can click a menu item to lower the menu, but cannot otherwise edit the menu bar directly in Design view. To edit a menu bar, double-click the menu item to display the Menu Designer.

Note: Menus (and menubar forms) are used only in the analyst interface. The customer and employee interfaces use a "launch bar" containing actual links, not drop-down lists. To modify the customer or employee launch bar, edit form std_body_site.htmpl from the appropriate interface.

Follow these steps:

  1. Select Tools, Menu Designer or double-click the menu shown in the Design tab of a menubar form.
    The Menu Designer dialog is displayed.
  2. Complete the fields in the Menu Designer dialog to add or edit menu items. For more information about adding menu items, see the Functions Useful in Menu Items topic.
  3. Click OK to close the dialog.
  4. Select Tools, Preview to check how the form is displayed to the end user. Although it resembles a standard CA SDM window, and most buttons and menus are functional, it is not a standard session, and you must not attempt to use it that way.
  5. Click File, Save.
    The menu bar is modified in the form.

Menu Design Dialog

The Menu Designer dialog appears when you select Menu Designer from the Tools menu, or double-click the menu shown in the Design tab of a menubar form. Use the Menu Designer dialog to add a menu bar, menus, submenus, and menu commands to the open form.

Note: You can access the Menu Designer only while editing HTMPL forms with a name beginning with “menubar_”, such as menubar_admin.htmpl.


The Menu Editor dialog contains the following controls:

  • Menu List
    From the menu list, select the menu item that you want to change. To change the menu label, for example, select a menu label from the list, type a new name in the Caption text box, and click Apply. You can add, insert, delete, and move the menu items using the controls in the Menu Designer. 

    Note: Only one level of indentation is possible.

  • Caption
    Enter the name for the selected menu item. See the property for more information.
  • Function
    Enter the JavaScript function to execute when the user clicks the menu. See the description of the Function property for more details, including some pre-defined functions that may be useful in menus.
  • ID
    Enter the HTML/JavaScript id to be assigned to the menu item.
  • Hot Key
    Enter a list of characters directing CA SDM’s selection of the hotkey for this menu item. The hotkey is underlined in the menu caption when it is displayed. CA SDM typically selects the first key in the menu caption not already in use as a hotkey. You can specify one or more characters here to restrict the selection to those characters, or specify one or more characters that are preceded by an explanation point to prevent selection of those characters.
  • Image
    Enter the location of the image that you want to appear next to the menu item.
  • Internal
    Select this option to specify that the JavaScript invoked by the function should be executed in the context of the current window (which could be a pop-up detail window). Leave this option unchecked to specify that the function should be executed in the context of the main form.
  • Variable
    Enter the JavaScript variable to be assigned to the menu item.
  • Tool Bar
    Adds a toolbar icon and tooltip that corresponds to a non-top-level menu item.
  • Icon File
    Identifies the location of the toolbar icon.
  • Tip
    Specifies the tooltip text.

Functions Useful in Menu Items

CA SDM provides a menu bar on almost every form to control its functions. The menu bar is generated by an HTMPL form with a name of the form menubar_xx.htmpl. We recommend that you use WSP to modify existing menu bars and define new ones.

The following predefined functions may be useful for scripts invoked by menu items:

  • upd_frame(form)
    Loads a new form into the main window content frame.
  • create_new(factory, use_template, width, height [,args])
    Pops up a form to define a new record.
    Popup_window(name, form[, width, height [,features [,args]]])
    Pops up a new window.
  • showDetailWithPersid(persid)
    Pops up a detail record.

The following terms and definitions apply to the previous functions:

  • Form
    This is either an HTMPL file name of the form xxx.htmpl or an operation code (for example CREATE_NEW).
  • factory
    This is the name of a database object.
  • use_template
    This is either true or false.
  • width
    This represents the desired form width or zero for default.
  • height
    This represents the desired form height or zero for default.
  • features
    This is a list of window features, in the same format used with the standard window.open function.
  • args
    This is one or more args of the form "keyword=value" for the operation specified for form.
  • persid
    This is a persistent ID in the form factory:ID.

Modify Style Sheets

You can use WSP to edit or create CSS (cascading style sheet) files.

Note: For performance reasons, CA SDM style sheets are delivered in two forms: Individual files (such as search_filter.css) and combination files grouping various individual files with comments and excess white space removed (such as analyst_styles.css). WSP always edits the individual files; you cannot edit a combination file directly. When you publish style sheet changes, WSP automatically builds the associated combination file if necessary.

Follow these steps:

  1. Create or open CCS style sheet file.
    WSP displays the Source view of the style sheet.
  2. You can edit directly in Source view, or can display the Style Designer by selecting Tools, Style Designer.
  3. Complete the fields in the Style Designer dialog, as appropriate. There are a number of style attributes, such as margin and border that cannot be seen or edited in the Style Designer. These must be edited in Source view.
  4. Click OK in the Style Designer.
    WSP reformats the style sheet and updates the Source view.
  5. Click File, Save.
    The style sheet is modified.

Style Designer Dialog

The Style Designer lets you modify or customize style sheets. By default the Style Designer dialog opens in the Font and Color tab and contains the following controls:

  • Style Classes
    From the drop down list, select a style element you want to modify.
  • Add
    Click to add a new style class.
  • Rename
    Click to rename the style class selected in the Style Classes drop-down list.
  • Delete
    Click to delete the style class selected in the Style Classes drop-down list.
  • Installed Fonts
    This property lists the fonts that are installed on the system. Click the left and right arrows to move the selected fonts between the Installed Fonts list and the Selected Fonts list.
  • Selected Fonts
    This property specifies a hierarchical list of preferred fonts that a browser uses to draw the style class element. A browser uses the first font in the list that is installed on the system it is running on.
    Click the up and down arrows to move the selected fonts up or down the hierarchy.
  • Font Size
    Select the font size from the drop-down list.
  • Bold
    Select a font style from the drop-down list.
  • Italics
    Select a font style from the drop-down list.
  • No Effect
    Select this option if you do not want any text decoration or special effects.
  • Underline
    Select this option if you want the text to be underlined.
  • Strikethrough
    Select this option if you want the text to appear with a line through it.
  • Overline
    Select this option if you want the text to appear with a line above it.
  • Foreground Color
    Select the foreground color for the text element by clicking the Browse button to the right of the Foreground Color property. Then select the color you want from the Color palette, and click OK.
  • Background Color
    Select the background color for the text element by clicking the Browse button to the right of the Background Color property. Then select the color you want from the Color palette, and click OK.
  • Transparent
    Select this option if you want the background of the style element to be transparent.

A sample of the style element is displayed in the preview area at the bottom of the dialog.

To set the position of the style element, click the Position tab. The Position tab contains the following controls:

  • Position
    From the drop-down list, select one of the positions for the element. The position property places an element in a static, absolute or relative position. Selecting a Static value will place the element in accordance with the normal flow. Selecting an Absolute value places the element anywhere on a page. Selecting a Relative value moves the element relative to its normal position.
  • Left
    Enter a value for the left margin in the text box for the element. Select a size from the drop-down list. This property is disabled when the selected position is Static.
  • Top
    Enter a value for the top margin in the text box for the element. Select a size from the drop-down list. This property is disabled when the selected position is Static.
  • Width
    Enter a value for the width in the text box for the element. Select a size from the drop-down list.
  • Height
    Enter a value for the height in the text box for the element. Select a size from the drop-down list.
  • Z-Index
    Enter a value for the stack order in the text box for the element. An element with greater stack order is always in front of an element with lower stack order. Z-index only works only on elements that have Absolute position

Note: Elements can have negative stack orders.

Click the Other tab to set some of the specific properties for the element. The Other tab contains the following controls:

  • Visibility
    Select the type of the visibility for the element from the drop-down list. The Visibility property sets how the content of an element is displayed if it overflows its area.
  • Overflow
    Select the type of overflow for the element from the drop-down list. The Overflow property sets what happens if the content of an element overflow its set area.
  • Display
    Select the type of the display for the element from the drop-down list. The Display sets how an element is displayed.
  • Cursor
    Select the type of cursor for the element from the drop-down list. The cursor property specifies the type of cursor to be displayed when pointing on an element.
  • OK
    Click to close this dialog and save your changes.
  • Cancel
    Click to close the Style Designer dialog.

Modify Mouse-Over Preview Form

The Mouse-over previews let you view key details within the current form without the need to click a link or open a new web page. The mouse-over preview appears when you place a cursor over an object link on a list or detail form for a certain amount of time. If you move the mouse away from the link before the delay time expires, the preview does not appear. Mouse-over previews appear by default on all list and detail forms in read-only mode.

You can create mouse-over previews for forms that do not have preview_ forms by default. You can also create mouse-over previews for custom forms you created in your CA SDM environment.

The following predefined mouse-over preview forms are available:

  • preview_chg.htmpl (Change Order)
  • preview_cnt.htmpl (Contact)
  • preview_cr.htmpl (Request)
  • preview_in.htmpl (Incident)
  • preview_iss.htmpl (Issue)
  • preview_KD.htmpl (Knowledge Document)
  • preview_nr.htmpl (Configuration Item)
  • preview_pr.htmpl (Problem)

Follow these steps:

  1. Open one of the following forms for the customization:
    • Open an existing form that does not have a preview_ form by default.For example, detail_loc.htmpl
    • Open an existing mouse-over preview form. For example, preview_chg.htmpl.
  2. Modify the form. For example, add or remove custom controls from the form.
  3. Click File, Save As, specify a file name using the preview_ prefix, and click Save. For example, enter preview_loc.htmpl.
    The mouse-over preview form is created and modified.

Modify Data Grid List on List Form

Data grid lists let you view the contents of a product page on a list form without opening a new page. This data-bound control lists items from the data source in a table so you can select items, sort items, and fetch data. For example, the expand and collapse options on the Incident List form.

Follow these steps:

  1. Open a list form.
  2. Locate the blue area after the labeled fields near the end of the form in the Design view. If you prefer Source view, the data grid appears between the following lines of code:

    <PDM_MACRO name=lsStart>
    <PDM_MACRO name=lsEnd>
    

    The following example shows this data grid area in Design view:

The plus sign in the data grid area represents the beginning of the expansion section of the row (the fields that are displayed only when a user clicks plus on the row in the list form grid). The following code generates the plus sign in the Source view:

<PDM_MACRO name=lsCol attr=open_date label="Open Date" sort="DESC" startrow=yes>

The startrow=yes parameter specifies to start a row, and it starts the expansion section of the row.

  • Drag-and-drop columns to move them in a list. You can move columns between the main part of the row and the expansion section. You cannot move an existing control after the grid area.
  • To insert a list column, right-click a control or anywhere within the blue background, and select either Insert Column or Insert Control.
    • If you select Insert Column, WSP inserts a column to the left of the currently selected control.
    • If you select Insert Control, WSP displays the Insert Control dialog that lets you add the desired control to the form.
  • Select Tools, Preview to verify how the form is displayed to the end user. Although it resembles a standard CA SDM window, and most buttons and menus are functional, it is not a standard session, and you should not attempt to use it that way.
  • Click File, Save.
    The data grid list is modified on the list form.

Modify Notebooks on Detail Form

The Nested tabs (notebook) control lets you expand or collapse key details within the current form. For example, use the control to customize how you organize tabs on the Incident Detail Form. From the Design View, you can use the Notebook control to add nested tabs to a detail form that does not already contain one. Double-click the Notebook control to modify it. Use drag-and-drop to add, insert, and delete notebook tabs, and to change their captions. You can also use the up and down arrow buttons to rearrange tabs by changing the position of the currently selected tab. The New Row check box specifies whether the selected tab begins a new row in the notebook header.

Follow these steps:

  1. Open a detail form.
  2. Locate the blue area of the form in the Design view that contains the first numbered label.
    If you prefer Source view, the notebook area appears between the following line of code:

    <PDM_MACRO name=startNotebook hdr=cng_nb>
    <PDM_MACRO name=endNotebook>

    Note: In CA SDM r12.6, a notebook can contain nested tabs. In WSP, a high-level tab (a tab containing other tabs) is named a tab group. WSP displays a tab group as a dark blue solid bar that spans the entire blue notebook area, with a numbered label in its center. A low-level tab (a tab that does not contain other tabs) is named a tab. WSP displays low-level tabs as rectangles with rounded corners.

     
  3. Click a tab to select it. Selecting a tab highlights and displays a link to the contents of the tab at the bottom of the notebook.
    You can move tabs and tab groups within a notebook using drag-and-drop. Moving a tab group moves all the tabs within the group with it.
  4. To insert a tab or tab group, right-click a control or anywhere on the blue notebook background and select Insert Tab, Insert Tab Group, or Insert Control.
    If you select Insert Tab or Insert Tab Group, WSP inserts a new tab or tab group to the left of the currently selected control. If you select Insert Control, WSP displays the Insert Control dialog that lets you add the desired control to the form.
  5. Select Tools, Preview to verify how the form is displayed to the end user. Although it resembles a standard CA SDM window, and most buttons and menus are functional, it is not a standard session, and you should not attempt to use it that way.
    Click File, Save.

Modify HTML and JavaScript Files

You can use WSP Source view to edit HTML and JavaScript forms.Open an HTML or JavaScript file and make the necessary changes.

Note: For performance reasons, some CA SDM JavaScript files are delivered in two forms: Individual files (such as window_manager.js) and combination files grouping a number of individual files with comments and excess white space removed (such as std_head.js). WSP always edits the individual files; you cannot edit a combination file directly. When you publish script changes, WSP automatically builds the associated combination file if necessary.

Migrate from Test to Production System

One of the design goals for WSP was to make it safe to develop and test forms modifications on a production database. Such features as a WSP-only directory tree on the server, dedicated WSP server processes, and read-only preview sessions support this goal. However, many users prefer to develop their forms modifications in an independent test system and then migrate the forms to a separate production system after they are complete as follows:

  1. Copy any HTMPL forms to be migrated from the appropriate subdirectory of site/mods/www/htmpl on the test system to the same subdirectory of site/mods/wsp/project on the production system.
  2. Copy any CSS, JavaScript, and HTML files to be migrated from the appropriate subdirectory of site/mods/www/wwwroot on the test system to the same subdirectory of site/mods/www/wwwroot/wsp/project on the production system.

    Note: Ensure that you copy the files and forms on the following servers of the production system, depending on your CA SDM configuration:
    • Conventional: Primary server
    • Advanced availability: Background server
Note: You can use any file copying method supported by your operating system to perform the copying described in steps 1 and 2 above. Windows users should substitute backslash (\) for slash (/) in the directory paths shown.

Publish Form Changes

When you are satisfied with the changes, you can make them available to all CA SDM users by publishing them. Publishing updates all CA SDM servers with new or revised forms.

Follow these steps:

  1. Select File, Publish.
    If you have any unsaved changes, WSP prompts you to save them, and then displays a confirmation dialog showing all pending Web Screen Painter changes (including those saved in previous sessions, or saved by other Web Screen Painter users). By default, all changes are selected for publication. You can change the selection of changes to be published by clicking them.
  2. Click OK when you are satisfied with the selection.
  3. (Advanced availability configuration only) If the webengine is not running on any of the CA SDM servers, an error message is displayed with the list of CA SDM servers on which WSP failed to publish. Complete the following steps:
    1. Configure the CA SDM server (the server specified in the error message) to make the corrections.
    2. Edit the file in WSP to add a white space character in the <PDM_IF 0> macro and save it.
    3. Go back to step 1 to republish the web form.

      Note: If you do not want to make any configuration changes, you have to manually copy the nx_root/site/mods/www folder from the background server to all the other servers.
  4. (Advanced availability configuration only) If the background server crashes while publishing, recover the HTMPL changes.
  5. (For mouse-over preview forms) Execute the following command after publishing the changes:

    pdm_webcache  - H
    

    The web cache is refreshed. WSP makes the selected changes available to all users active on all the servers.

Note: Only site-modified forms can be deleted. Requests to delete a previously published form take effect when you publish changes. To cancel a pending delete request, select File, Undelete Form. You undo changes to a form after publication.

Recover the HTMPL Changes

You recover the HTMPL changes when the background server fails during the publishing activity.

Important! We recommend you not to perform the recovery steps directly on the production environment. Ensure that you first validate them on the test or development environment.

Follow these steps:

  1. Go to the following directory on the crashed background server:

    $NX_ROOT$/site/mods/www/wwwroot/wsp/project/web
  2. Copy all the content from the web folder.
  3. Log in to the new background server and paste all the copied content in the $NX_ROOT$/site/mods/www/wwwroot/wsp/project/web folder.
  4. Resume publishing the changes on the new background server.
Was this helpful?

Please log in to post comments.