Skip to main content

 –

Configuring Microsite settings

Suggest edit Updated on September 21, 2021

If you have installed the MS.war file on a different machine than the one on which you have deployed Pega Customer Decision Hub, you need to modify the index.html file.

Note: Only operators who have the role PegaMarketing_FW:MicrositeAdmin can create Microsites. By default, analysts do not have this role. If an operator requires the ability to create Microsites, associate the operator with an access group that contains the PegaMarketing_FW:MicrositeAdmin role (see Pega Platform help or go to Pega Community for instructions on configuring access groups).
  1. Navigate to the directory where the MS.war file has been deployed. For example: Tomcat\webapps\MS
  2. Edit the index.html file and prepend the full URL to your system:
    • http://hostname:port/prweb?pyActivity=pzIncludeMashupScripts
    • http://hostname:port/prweb/PRRestService/PegaMKTMicrosite/Services/IncludeMicrositeScripts
  3. In Dev Studio, open the application rule associated with the PegaNBAM:Agents access group.
  4. In the application rule, go to the Integration & Security tab.
  5. In the Mashup security section, add a new Trusted Origin and add the URL for the location of the deployed MS.WAR file.
  6. If you previously configured a content security policy in the Content security section, edit the policy and allow access from the website where the MS.war file has been deployed.
    You must update the Frame-Ancestors section of the policy on the Policy Definition tab, and potentially other sections, if required by the Microsite.
  7. Click ConfigureSystemGeneralSystems, Nodes, Requestor.
  8. In the Requestors table, click the BROWSER requestor for your current system.
    Note: Your current system name is displayed in the System Name field above the table.
  9. Click Save.
  10. Create a new operator account. In the Access Group section on the Profile tab, enter or select <your application>:Microsites.
  11. Create the following Dynamic System Settings to override the default configuration settings in the Microsite gadget:
    The owning ruleset for all of the settings is PegaMKT-Engine.
    • microsite/applicationname - This is the application name which the Microsite gadget uses when connecting to Pega Customer Decision Hub. By default, it is the name of the application associated with the access group on the PegaMKTMicrosite service package.
    • microsite/URL - This is the URL which the Microsite gadget uses when connecting to Pega Customer Decision Hub. The URL should point to an IAC servlet on the public node. The URL format is http://<hostname>:<port>/prweb/IAC.
    • microsite/deployedURL - This is the URL where the MS.War file was deployed. The URL format is http://<hostname>:<port>/MS.
    • microsite/systemid - This is the system ID which the Microsite gadget uses when connecting to Pega Customer Decision Hub. By default, it is the system ID defined on the system which the URLs point to.
    • microsite/defaultclass - If the Site parameter of the Microsite URL is not defined, this setting purpose is used instead.
    • microsite/parameters/useridentifier - This is the user which the Microsite gadget uses to authenticate itself with Pega Customer Decision Hub. Enter the name of the operator you created in step 11 into the Value field.
    • microsite/parameters/skinname - This is the name of the skin used by the Microsite.Note: If you are using your own skin to update the included styles tab of the skin rule, select the check box Include legacy CSS. Without the legacy CSS, your skin will not be displayed on multi-node environments.
    • microsite/parameters/additional - This is a comma-separated list of additional parameters that can be passed to the gadget.
    • Previous topic Configuring access groups and roles
    • Next topic Optional: Granting permission to configure ethical bias policies
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us