Policy Server Guides › Policy Server Administration Guide › Policy Server Tools › Import Policy Data Using smobjimport

Import Policy Data Using smobjimport

You can use the smobjimport tool to import the entire policy store or a single policy domain.

Follow these steps:

1. Navigate to one of the following locations:
   • On Windows, SiteMinder_installation\bin

   SiteMinder_installation

   Specifies the installed location of SiteMinder.

   • On Unix, SiteMinder installation/bin

   SiteMinder_installation

   Specifies the installed location of SiteMinder.

2. Enter the following command:

   smobjimport -ifile_name -dadmin-name -wadmin-pw -v -t
   

   Example: smobjimport -ipstore.smdif -dSiteMinder -wpassword -v -t

   Important!

   • If the file you are importing contains sensitive data in clear-text, the following option is required to import the data:

     -c
     

     Failure to use this option can corrupt the policy store.

   • You only need to enter the .smdif file with the smobjimport command, since it automatically imports both the .smdif and .cfg files together if they are in the same directory. The environment properties stored in the .cfg file take precedence over the ones in the .smdif file. Thus, you can overwrite an environment’s data by pairing the .smdif file with a different .cfg file when running smobjimport.

Overview of the XML-based Data Format

Enterprise environments can require policy store data to be moved from one environment to another, such as from a development environment to a staging environment. In releases prior to r12, policy objects are represented using the proprietary SiteMinder Data Interchange Format (SMDIF), using smobjimport and smobjexport for migrating the data. This export format and these tools have been replaced by an XML-based export format, using XPSExport and XPSImport to migrate the data.

The XML-based export format uses the following fundamental schemas:

XPSDeployment.xsd

Describes the top-level schema, which includes the other schemas. It defines the root element and sub-elements. An XML file conforming to this schema can contain an instance of Data Dictionary, Policy, and Security Data.

XPSDataDictionary.xsd

Describes meta-data information about object types and their properties.

XPSPolicyData.xsd

Describes the meta-data information about objects stored in the policy store, such as domains, policies, rules, applications, and the relationships between them.

XPSSecurityData.xsd

Describes meta-data used for representing policy store administrators and their access rights.

XPSGeneric.xsd

Contains definitions of the generic data types used in the other schema files.

This format supports not only exporting and importing policy data in its entirety, but also exporting and importing a subset of the policy data. A granular export presupposes knowledge of how the data will be imported. On export, you can specify the entire policy data, or a portion of the data using an object identifier and optionally one of these three export types:

• Add—specifies that only additions can be done during import.
• Replace—specifies an overwrite of existing policy data during import.
• Overlay—specifies that updates to policy data are done during import.

Note: The XPSExport and XPSImport tools encrypt sensitive data based on the FIPS mode the Policy Server is operating in. There are no additional parameters in these tools to set for data encryption.

More information:

XPSImport