PortalPromotionsubdirectory within your equivalent of SAS-Configuration-Directory
\Lev1\Web\Applications\SASPortal<ver>\. 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.
@Nameparameter by specifying the user's name. Here is an example:
<Tree search="*[@Name='Analyst Permission Tree']" TemplateName="PortalPermissionsTree"/>
Nameparameter must match the exact name for the User Permissions Tree. If you need to obtain the correct name for the User Permissions Tree, access SAS Management Console. Then, navigate to Environment ManagementUser Manager. Select the Show Users check box to display the user names.
set SAS_HOME=C:\Program Files\SAS-Installation-Directory set JAVA_HOME=C:\Program Files\Java\jre1.5.0_15\
extractPortal913.bat(for a SAS 9.1.3 source on Windows),
extractPortal92.sh(for a SAS 9.2 source on UNIX), or
extractPortal93.sh(for a SAS 9.3 source on UNIX). For more information, see About the Portal Promotion Tools.
PermissionsTree_extract.xmlfile. Verify that the user or group name is accurate in that file. DBCS characters typically appear in certain languages including Hebrew, Chinese, or Japanese.
ReposIDparameter with the target system's metadata repository ID. As a result, commands that import portal content will verify that the target repository does not contain duplicate content.
build.propertiesfile to customize and provide the values for the metadata repository IDs, the SAS Administrator accounts, and the SAS Trusted User accounts. Here is an example of the
xml.file=PermissionsTree source.reposid.of.metadata.repository=A0000031.A5BQ25K2 target.reposid.of.metadata.repository=A0000001.A5T8FYJJ source.sasadm.name=SAS Administrator target.sasadm.name=sasadm source.sastrust.name=SAS Trusted User target.sastrust.name=sastrust
build.propertiesfile, skip this step. If you did not modify the
build.propertiesfile (because the source is a SAS 9.1.3 or SAS 9.2 system, and the default values for the SAS Administrator and the SAS Trusted User were previously customized and modified in the source or target deployments), then you should manually specify the values for these internal accounts in these generated .xml files:
@Nameparameter as it applies to the SAS Administrator and SAS Trusted User. Note that some .xml files might not require these values for the
build.propertiesfile, skip this step. When you run the upgrade metadata commands later, the generated .xml files are updated with the required values. If you manually updated the values in the .xml files, open the
PermissionsTree_deployFile.xmlfile. Search for the
RepositoryBase Deploy_Idparameter. Specify the target system’s metadata repository ID as the value for
RepositoryBase Deploy_Idand the target systems’s metadata name as the value for the
Deploy_Nameparameter. Here is an example:
<Repository Base Deploy_Id="A0000001.A5T8FYJJ" Deploy_Name="Foundation" Id="A0000031.A5BQ25K2" Name="Foundation"/>
importPortalversion.bat PermissionsTree.xml -user ID -password AdminPwd
build.propertiesfile, upgrade the portal metadata with a single command. See Upgrade the Portal Metadata After Editing the build.properties File.
build.propertiesfile, run the following upgrade command:
upgradeMetadata updateXMLSource -user ID -password AdminID
build.propertiesfile to update the values in these files:
-user ID -password AdminPwd -trusted_user sastrust@saspw1
|1The trusted_user parameter uses the logon password that is used for the SAS Trusted User account. Typically, this default password is sastrust@saspw.|
manualLoadContent-OrderNumber and the
manualAdjustUrls–OrderNumber scripts are available for converting data explorations and bookmarks to reports. These scripts are located in the SAS-Configuration-Directory