Preparing to Use the Promotion Tools

Ensure That the Required Servers Are Present

Before using the export and import wizards (or the batch export and import tool), make sure that the appropriate servers exist and are running, as follows:
  • The object spawner must be running in both the source environment and the target environment.
  • If you are promoting physical content that is associated with stored processes, tables, jobs, libraries, or external files, then a standard (non-pooled) workspace server must exist in both the source environment and the target environment.
  • If your stored processes create packages that are stored permanently on the SAS Content Server, then a SAS Content Server must exist and must be running in both the source environment and the target environment.
  • If you are promoting reports and want to store report content on a SAS Content Server, then a SAS Content Server must exist and must be running in both the source environment and the target environment.

Ensure Appropriate User Credentials

Make sure that the user who launches the wizard (or whose credentials are specified in the batch export or import command) has the following credentials and permissions:
  • ReadMetadata access to the objects that are being exported
  • WriteMetadata access to the objects that are being imported
  • WriteMemberMetadata access to the folders where objects are imported
  • appropriate access to associated physical content (for example, tables and source code files) that is being exported or imported
  • credentials to access the workspace server, if you are exporting or importing physical content that is associated with stored processes, tables, jobs, libraries, or external files (see Requirements for Accessing a Standard Workspace Server)
    Note: If your user account does not have workspace server credentials, the wizard prompts you to enter additional credentials. For example, you will be prompted to enter additional credentials if you are running the wizard using an internal account (a user ID with the suffix @saspw).

Ensure Adequate Memory

If you are planning to export or import a large number of sizable objects, then you might need to increase the amount of memory that is allocated to the import or export process. Information maps, SAS Data Integration Studio jobs, and tables are the object types that most frequently require additional memory. To increase allocated memory, follow these steps:
  1. On the client machine where you are executing the export or import, open the appropriate INI file in a text editor as follows:
    • If you are using SAS Management Console, open sasmc.ini, which is located in SAS-installation-directory\SASManagementConsole\9.3.
    • If you are using SAS Data Integration Studio, open distudio.ini, which is located in SAS-installation-directory\SASDataIntegrationStudio\4.3.
    • If you are using SAS OLAP Cube Studio, open olapa.ini, which is located in SAS-installation-directory\SASOLAPCubeStudio\4.3
    • If you are using the batch import or export tool, then open ImportPackage.ini or ExportPackage.ini. These files are located in SAS-installation-directory\SASPlatformObjectFramework\9.3.
  2. Locate the following line:
    JavaArgs_1=-Xmx512m
  3. Replace 512 with a higher value (for example, 1024), and save your changes.
    Note:
    • For SAS Management Console and SAS Data Integration Studio, this value is set to 1024 by default. For the batch tools and SAS OLAP Cube Studio, the default value is 512.
    • If your desktop applications run in the Citrix application delivery environment, then you can increase the size of your Java heap to the Citrix limit. All versions of Citrix support a maximum Java heap size of 512 megabytes, and some versions support higher limits.
As an alternative to increasing memory, you can perform multiple imports or exports that include a smaller number of objects instead of importing or exporting all of your objects at the same time.

Set Up Security for Folders and Objects

In some cases, you might want to set up and test access controls for folders or objects in the source environment, and then include these access controls in the promotion. To use this approach, see Promoting Access Controls.
As an alternative, you might want to set up folders on the target metadata server and apply access controls to them before you import your metadata.

Create Directories for Physical Files on the Target System

On the target system, set up directories for the physical content that you plan to promote with the metadata. For example, you might need to create directories for the following:
  • physical locations of libraries
  • physical files and external format files (EFFs) that are associated with external files
  • custom code that is associated with jobs, if the code is stored outside of the metadata
  • source code repositories for stored processes
  • File or directory prompts for which a default file or directory value is specified (see Promoting Prompts)
The user who will execute the import should have Write access to these directories.
Copyright © SAS Institute Inc. All rights reserved.