Previous Page | Next Page

Promoting Portal Content

Promote the Entire Portal Application Tree

About Promoting the Entire Portal Application Tree

You can promote an entire portal application tree in either of the following scenarios:

The advantage of promoting the entire Portal Application Tree is that it is comprehensive. All supported content types are promoted together. You do not have to keep track of dependencies among those content types or follow a specific sequence in order to preserve those relationships.

CAUTION:
Promoting the entire Portal Application Tree causes all users to lose all of their Portal personalizations (such as preferences, layout customizations, and favorites).

Due to this limitation, this approach is not ideal for regular or frequent promotions.  [cautionend]

The promotion process is as follows:

Step 1: Prepare the Source System

Step 2: Extract Content from the Source Metadata Repository

Step 3: Prepare the Target System

Step 4: Import Content into the Target Metadata Repository

Step 5: Upgrade the Portal Metadata in the Target Repository

Step 6: Clean Up and Validate

Step 1: Prepare the Source System

To prepare the source system for portal promotion, follow these steps:

  1. Perform a complete backup of the source system (including the metadata repository, the configuration directories, and the WebDAV).

    Note:   For instructions, see the SAS Intelligence Platform: System Administration Guide. Use either the SAS 9.1.3 or SAS 9.2 version of this document, as appropriate for the version of your source system.  [cautionend]

  2. If the source system does not contain the SAS-Configuration-Directory\Lev1\Web\Applications\SASPortalVersion\PortalPromotion directory, create this directory path. For example, on a source SAS 9.1.3 system, create this directory path:

    SAS-Configuration-Directory\Lev1\Web\Applications\SASPortal4.2\PortalPromotion

    Copy the promotion scripts into that directory. The portal promotion scripts use the directory paths specified for the JAVA_HOME and the SAS_HOME environment variables.

    • If you have SAS Information Delivery Portal 4.3, the scripts are in the configuration directory under your equivalent of \Lev1\Web\Applications\SASPortal4.3\PortalPromotion

    • If you do not have SAS Information Delivery Portal 4.3, obtain the scripts by contacting SAS Technical Support.

    Note:   The scripts use relative paths, so it is essential that they are present in the correct location.  [cautionend]

  3. Edit the source copy of the PortalPromotion\PortalApplicationTree.xml file so that it points to the source metadata repository.

    1. Locate the source metadata repository's ID. In SAS Management Console, you can find the ID by navigating to Metadata Manager [arrow] Active Server and selecting Foundation. The repository ID is displayed in the right panel and consists of two 8-digit numbers separated by a period (for example, A0000031.A5BQ25K2).

    2. Edit the PortalApplicationTree.xml file to specify the source metadata repository's ID in the ReposId parameter. For example: <ReposId>A0000031.A5BQ25K2</ReposId>

Step 2: Extract Content from the Source Metadata Repository

To extract content from the source metadata repository, follow these steps:

  1. Open a host command window.

  2. Set environment variables for SAS_HOME and JAVA_HOME. For example:

    set SAS_HOME=C:\Program Files\SAS\SASFoundation\9.2
set JAVA_HOME=C:\Program Files\Java\jre1.5.0_15\bin

    or 

    export SAS_HOME=/disk2/SAS9.2/SAS-Installation-Directory/SASFoundation/9.2
export JAVA_HOME=/usr/java/jdk1.5.0_07/bin/java

    Note:   The JAVA_HOME environment variable must be set to match the version used by the Web application server.  [cautionend]

  3. Run the appropriate extraction command:

    extractPortalversion.bat PortalApplicationTree.xml  -user ID  -password AdminPwd

    or

    extractPortalversion.sh  PortalApplicationTree.xml  -user ID  -password AdminPwd

    Note:   Choose the version of the script that matches your source. For example: extractPortal913.bat (for a SAS 9.1.3 source on Windows), or extractPortal92.sh (for a SAS 9.2 source on UNIX). For more information, see About the Portal Promotion Tools.  [cautionend]

    The extraction script generates the following files:

    • PortalApplicationTree_deployFile.xml

    • PortalApplicationTree_expand.xml

    • PortalApplicationTree_extract.xml

    • extract.log

  4. Open the extract.log file and verify that the file does not contain any errors. If XML files are not generated, the extract.log file should provide an explanation.

  5. If the target is on a different machine or platform from the source, copy the extracted XML files to the PortalPromotion directory on the target host.

Step 3: Prepare the Target System

To prepare the target system, follow these steps:

  1. Perform a complete backup of the target system (including the metadata repository, the configuration directories, and the WebDAV). For instructions, see the SAS Intelligence Platform: System Administration Guide.

  2. To obtain the metadata repository ID on the target SAS 9.2 system, follow these steps:

    1. On the SAS Management Console on the target system, right-click Foundation, and select Properties.

    2. Expand Metadata Server Active Manager. The metadata repository ID is displayed in the dialog box. (for example, A0000031.A5BQ25K2).

    3. Make a note of the metadata repository ID so that you can specify it in the appropriate .xml import files.

      CAUTION:
      If the metadata repository ID in .xml import files is different from the metadata repository ID on the target system, the import processes will fail.   [cautionend]

  3. If the target system's version is different from the source system's version (for example, you are promoting content from a SAS 9.1.3 system to a SAS 9.2 system), install the following JAR files in the ANT_HOME/lib directory:

    • bsf.jar

    • BeanShell JAR files: bsh*.jar

    • commons-logging.jar

    You can obtain JAR files from the following locations:

    On Windows: SAS_Installation_Directory \Program Files\SAS\SASVersionedJarRepository\9.2\eclipse\plugins

    On UNIX: SAS_Installation_Directory/SASVersionedJarRepository/9.2/eclipse/plugins

    JAR files can also be obtained from http://ant.apache.org/manual/install.html. In the section on Library Dependencies, click the appropriate URL paths to download each set of JAR files.

  4. Open the PortalApplicationTree.xml file located in the SAS-Configuration-Directory\Lev1\Web\Applications\SASPortal4.3\PortalPromotion directory.

  5. Search for the ReposId parameter. Replace the metadata repository ID with target system's metadata repository ID, and save the file. Here is an example of the ReposID parameter: 

    <ReposId>A0000001.A5T8FYJJ</ReposId>

  6. If the operating system is UNIX, open the PortalApplicationTree_deployFile.xml file. Search for the RepositoryBase Deploy_Id parameter. Specify the target system's metadata repository ID as the value for RepositoryBase Deploy_Id and the target system's metadata name as the value for the Deploy_Name parameter. Here is an example: 

    <RepositoryBase Deploy_Id="A0000001.A5T8FYJJ"
Deploy_Name="Foundation" 
Id="A0000031.A5BQ25K2"
Name="Foundation"/>

  7. If the source is a SAS 9.1.3 system, modify the SAS 9.2 metadata as necessary to ensure that the SAS 9.2 user and group names align with the SAS 9.1.3 metadata. In particular, you must adjust the metadata Name of the SAS Administrator and the SAS Trusted User in your SAS 9.2 repository. The groups and users that exist on the source system must also exist on the target system. For example, if a PortalAdmins group exists on the source system with the SAS Web Administrator and SAS Administrator, the same group with these users should exist on the target system. After the completion of the import process, these users and groups can be modified or deleted.

    Note:   Any users or groups that exist only in the target are unaffected by the promotion.  [cautionend]

  8. Verify that the portlets that are going to be imported have already been registered and deployed in the target system. Portlets exist independent of the Portal Application Tree, so they are not within the scope of its promotion.

  9. Ensure that all SAS content that needs to be associated with the incoming portal data is present in the target. This step is essential to success and can require significant effort. This step involves tasks that are outside the scope of the portal promotion process. See What Cannot Be Promoted through Portal Promotion.

    Note:   As part of this effort, make sure that the supporting SAS content is at the appropriate version level. For example, beginning with the 4.3 release of SAS Information Delivery Portal, data explorations must be converted to reports. Typically, this conversion occurs during a migration or an upgrade to SAS Information Delivery Portal 4.3. If you did not convert data explorations to reports, you will need to manually update the content and adjust directive URLs. Because data explorations can have dependencies on OLAP cubes, make sure the cubes have been built after your migrate. This task should be done before you run the scripts for updating content and adjusting directive URLs. For more information, see "Server Tier Post-migration Tasks" in the SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide. Also, see Update Content Manually for the SAS Content Server.  [cautionend]

  10. If the Portal Application Tree exists on the target system, remove it:

    removePortal92.bat PortalApplicationTree.xml  -user AdminID  -password AdminPwd

    or

    removePortal92.sh PortalApplicationTree.xml  -user AdminID  -password AdminPwd

    CAUTION:
    This action is irreversible.   [cautionend]

Step 4: Import Content into the Target Metadata Repository

To import content into the target metadata repository, follow these steps:

  1. Open a host command window.

  2. Set the JAVA_HOME and SAS_HOME environment variables.

  3. Run the appropriate import command:

    importPortal92.bat PortalApplicationTree.xml  -user ID  -password AdminPwd

    or

    importPortal92.sh  PortalApplicationTree.xml  -user ID  -password AdminPwd

    Note:   You can import only into a SAS 9.2 system, so you always use the SAS 9.2 script. For more information, see About the Portal Promotion Tools.  [cautionend]

  4. Review the feedback in the output command window. This output is also saved in the import.log file that is located in the PortalPromotion directory.

Step 5: Upgrade the Portal Metadata in the Target Repository

To upgrade the portal metadata in the target repository, follow these steps:

  1. Open a host command window.

  2. Set the ANT_HOME environment variable.

  3. Run the upgrade commands, in order.

CAUTION:
Complete this step only if the source is not at the appropriate version level.   [cautionend]
Commands for Portal Metadata Upgrade
Command (for UNIX use .sh instead of .bat) Parameters
upgradeMetadata.bat convertAces -user ID -password AdminPwd -trusted_user sastrust
upgradeMetadata.bat renameAlertsPortlet -user ID -password AdminPwd
upgradeMetadata.bat fixDav -user ID -password AdminPwd
upgradeMetadata.bat deleteOrphanedForeignKeys -user ID -password AdminPwd
upgradeMetadata.bat reparentPermTrees -user ID -password AdminPwd
upgradeMetadata.bat movePublicKioskInfo * -user ID -password AdminPwd
upgradeMetadata.bat convertIMVtoReportPortlet * -user ID -password AdminPwd
upgradeMetadata.bat adjustUrls * -user ID -password AdminPwd
* Run this command only if you are upgrading to the 4.3 version of SAS Information Delivery Portal from another version of that product.

For more information, see About the Portal Promotion Tools.

Step 6: Clean Up and Validate

To clean up and validate, follow these steps:

  1. Apply the Portal ACT to the Portal Application Tree. In SAS Management Console, follow these steps:

    1. Log on to SAS Management Console as the SAS Administrator.

    2. Navigate to Authorization Manager [arrow] Resource Management [arrow] By Type [arrow] Tree, select Portal Application Tree, and right-click and select Properties.

    3. In the Portal Application Tree Properties dialog box, click Authorization.

    4. Click Access Control Templates.

    5. In the Add and Remove Access Control Templates dialog box, expand the Foundation node in the panel on the left.

    6. Select Portal ACT, and move it to the panel on the right.

    7. Click OK to save your changes.

  2. In the target system, undo any modifications to metadata that were made only for the purpose of the promotion (for example, any changes that were made to the unrestricted name, trusted name, and Portal Admins group).

  3. Verify the following results to determine the successful importing of the Portal Application Tree:

    • The Public Kiosk page was created as a shared page for all users.

    • The Public guest page was created.

    • Guest content for public is moved to the SAS Guest User account.

    • WebDAV content and graph portlets moved successfully after DAV content is imported.

    • The DAV content for reports moved over to SAS Folders.

    • The DAV folder locations were successfully updated from WebDAVDemo to WebDAV.

    • Data explorations work after content was made available.

    • Bookmarks are available for SAS Information Maps and for SAS Web Report Studio reports.

    • Existing SAS BI Dashboard portlets successfully use the content and data.

Previous Page | Next Page | Top of Page

Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.