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

Import Policy Data Using smobjimport

The smobjimport tool imports the entire policy store or a single policy domain using two files--an .smdif (SiteMinder Data Interchange Format) and a .cfg (environment configuration) file--created by smobjexport. The .smdif file standardizes SiteMinder data so you can import it into an ODBC or LDAP directory. For example, you can export an .smdif file from an ODBC database and import it to an LDAP directory. The environment configuration (.cfg) file contains environment specific properties for the policy store such as the IP Addresses, redirection URLs, shared secrets, and logging settings. The text in the .cfg file is separated by tabs and you can read it in an Excel spreadsheet.

Using the Command Line Interface, you can write Perl scripts to import and export particular objects rather than all the Policy Store objects. For more information, see the SiteMinder Programming Guide for Perl.

Note: The naming convention for smobjimport is the same as smobjexport in that it supports an .smdif file and .cfg file. Using smobjexport as an example, if the output file you specified with the smobjexport command has an .smdif extension (that is, file_name.smdif), then the extension is replaced with .cfg (such as file_name.cfg) for the configuration file. However, if the output file you specify does not have an .smdif extension (that is, file_name.txt), then .cfg is appended to file name and extension (such as file_name.txt.cfg).

smobjimport uses the following arguments to supply information required to import data:

• -4

  Allows you to import policy store data from SiteMinder 4.51/4.61.

• -ifile_name

  Specifies the path and file name of the input .smdif file.

• -f

  Indicates that duplicate information should be overwritten. Be careful using this argument as it enables you to overwrite default SiteMinder objects that may have been imported into a new policy store by using smpolicy.smdif.

• -c

  Indicates that the input file contains sensitive data in clear-text. This argument allows to you import policy data from a SiteMinder deployment that uses one encryption key to another SiteMinder deployment that uses a different encryption key. This option requires the credentials of a SiteMinder administrator who can manage all SiteMinder domain objects. Enter credentials using the -d and -w arguments.

• -dadmin-name

  Specifies the login name of a SiteMinder Administrator that can manage all SiteMinder objects.

• -wadmin-pw

  Specifies the password of the SiteMinder Administrator specified in -d.

• -k

  Imports Agent keys stored in the policy store. If you import using this argument, and the policy store to which you are importing already contains keys, single sign-on for existing users may be interrupted. Note that keys are created each time you start the Policy Server.

• -v

  Enables verbose mode.

• -t

  Enables low level tracing mode. This can be used to troubleshoot the import process.

• -l

  Creates a log file. Make sure the file_name.smdif file ends with an .smdif and not a .txt or other extension. If the file_name.smdif file ends with an .smdif extension, smobjimport creates a log file with a .log extension. However, if the file_name.smdif file ends with a .txt extension, smobjimport creates a file_name.txt.log file, which is incorrect since the log file must be in the file_name.log format.

• -r

  Turns off automatic renaming of objects. By default, when smobjimport attempts to import an object with a name that already exists in the target policy store, it creates a duplicate object with a name of nameoid, where name is the name of the object, and oid is the object ID of the new duplicate object. If you use this flag to turn off the automatic renaming feature, smobjimport returns errors messages for any objects that could not be created because of naming conflicts.

• -u

  Import variables only.

• -m

  Import IdentityMinder objects only.

• +m

  Import SiteMinder objects only.

• -?

  Displays the help message.

• -a1

  Disables object store validation and helps increase the speed at which objects are imported.

  Important! This parameter should only be used when importing data into a new policy store and when the imported .smdif file is consistent with regards to policy store objects.

• -a2

  Disables object store auditing and helps increase the speed at which objects are imported.

• -a3

  Disables object store cache updates and helps increase the speed at which objects are imported.

  Important! Do not use this parameter when importing data into an existing policy store with more than one policy store pointing at it. Using this parameter disables cache synchronization between the Policy Servers.

• -a

  Same as setting -a1, -a2, and -a3 together.

  Important! This should only be used on a new policy store. Do not use this parameter when importing data into an existing policy store since it could corrupt the policy store.

Note: If any of the arguments contain spaces, use double quotes around the entire argument. For example, if the name of the SiteMinder administrator is SiteMinder Admin, the argument for smobjimport would be -d"SiteMinder Admin". If the description of a SiteMinder object specified in the Administrative UI is more than one line long, smobjimport will only import the first line of the description.

To import Policy data using smobjimport

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

   Note: 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.