Set Up a Second Deployment Instance of SAS Web Report Studio

Create the New Deployment Instance
Configure Application Properties for the New Deployment Instance

Create the New Deployment Instance

During installation, the SAS Deployment Wizard creates one SAS Web Report Studio deployment instance. To create an additional deployment instance, you rerun the SAS Deployment Wizard.
Follow these guidelines:
  • Create the new deployment instance on a second middle-tier machine (to avoid JVM port and context root conflicts between the two deployment instances).
  • Use a deployment plan that contains the SAS middle tier.
  • You must choose the Custom configuration prompting level.
  • Provide connection information for the metadata server that you are currently using (the new deployment instance uses your existing SAS Metadata Server).
  • Provide the correct machine name on which you are adding the SAS Web Report Studio deployment instance.
  • Give the second SAS Web Report Studio deployment instance a name such as RestrictedWRS. Each deployment instance name must be unique. If you leave this field blank, or provide a name that is already in use, the configuration fails.
For more information about the SAS Deployment Wizard, see the SAS Intelligence Platform: Installation and Configuration Guide.

Configure Application Properties for the New Deployment Instance

  1. Configure the RestrictedWRS deployment instance of SAS Web Report Studio to use client-side pooling.
    1. On the Plug-ins tab, expand Application Managementthen selectConfiguration Manager. Right-click the RestrictedWRS deployment of SAS Web Report Studio and select Properties.
    2. Select the Settings tab. On the left side, select Applicationthen selectPooling. On the right side, set the client-side pooling option to Yes.
      Note: If you are not able to change this setting, click Cancel. Under Configuration Manager, right-click SAS Application Infrastructure, navigate to its client-side pooling setting, and click the Lock icon (to unlock it). Then return to the properties of the RestrictedDataReporting deployment instance of SAS Web Report Studio, and turn on client-side pooling.
    3. On the Advanced tab, as the Property Value for the App.ClientSidePoolingAdminID property, enter the user ID for the pool administrator (rpooladm).
      Tip
      On Windows, qualify the user ID (for example, WIN\rpooladm).
  2. Constrain the RestrictedWRS deployment instance of SAS Web Report Studio so that it accepts relational information maps from only a designated, protected location in the SAS folders tree.
    1. On the Advanced tab, click Add and use the Define New Property dialog box to add he following properties and values:
      Property Name
      Property Value
      wrs.map.accessibility.check.enabled
      true
      wrs.map.accessibility.check.rootlocations
      path1
      1For example, SBIP://METASERVER/rlp/RestrictedMaps. To designate multiple locations, enter a comma-separated list. This restriction does not affect OLAP information maps.
    2. In SAS Management Console, create the designated folder (if it does not already exist). On the folder’s Authorization tab, perform the following tasks:
      • Explicitly deny the WriteMetadata and WriteMemberMetadata permissions to PUBLIC.
      • Explicitly grant the WriteMemberMetadata permission to only those users and groups who should be able to add and update the sensitive relational information maps.
      • Make sure that end users of reports based on the secure information maps have ReadMetadata access.
  3. To make the application properties changes take effect, restart the web application server.
Copyright © SAS Institute Inc. All rights reserved.