A specific Configuration Profile node corresponds to an instance of a complete
component store configuration (for example, Default Certificate Store).
The set of Versions for that Configuration Profile that have been saved over time are
listed under the component store node. You can access the following configuration
options by right-clicking a component store node or its most recent Version node
in the tree:
Edit:
Opens this component store in the Profile Editor for editing so that
its policies, certificates, and so on, can be updated. The latest Version is opened
when this option is selected on the component store node. All updates applied
are saved to a local copy of the configuration file. This option is available
if more than one component store is selected in the tree (or table) with the result
that all selected component stores are simultaneously loaded into the Profile
Editor.
Commit Version:
This option is only enabled after the component store configuration is loaded in the
Profile Editor. When you commit a Configuration Profile, you are asked to
enter a Comment. When you commit your changes, the local Configuration Profile is returned
to the currently managed server (for example, Enterprise Gateway), and a new Version is created. A
new Version node is added under this configuration node. You can also use the Commit
Version menu option in the Profile Editor tab from the top-level
node for that Configuration Profile.
If you make local changes that are not committed, you are asked if you wish to load
your local version or the server version the next time you load the Configuration Profile.
This enables you to retrieve local changes if your session times out before you
commit the changes.
Create via Copy:
A copy of the latest Configuration Profile Version is taken and used to create a
new Configuration Profile. You must enter a name for the Configuration Profile. A new
Configuration Profile node is displayed under My Configuration Profiles.
Rename:
You can rename the Configuration Profile by specifying a new name in the Rename
Configuration Profile dialog.
Change Owner:
You can change the ownership of the Configuration Profile. When ownership changes, the
configuration node moves into the other User's My Configuration Profiles
node. This option is available if more than one Configuration Profile is selected in the
tree (or table).
Export:
You are asked to enter a filename to export to. The latest Version of the Configuration
Profile is exported to this file, which you can then import into a different
Enterprise Gateway configuration. For example, this is useful if you have configured the
Enterprise Gateway in a testing environment, and want to move this configuration to a live
production environment.
Archive:
Archives the Configuration Profile and all of its related Versions. The
configuration node is removed from the tree. This option is only
available if none of the Versions related to this Configuration Profile are
deployed. Note that you can not delete a Configuration Profile.
When the Policy Studio receives a request to archive a Configuration Profile, the
underlying files that hold the Configuration Profile and its Versions are moved
into the INSTALL_DIR/conf/archive directory on the Policy Studio
machine. The underlying configuration data used by the Policy Studio is deleted.
The system administrator must determine whether to remove these files from disk
and store them elsewhere for backup purposes. If there is a requirement to reload
an archived Configuration Profile or one of its Versions, the archived file must
be located manually and re-imported to create a new Configuration Profile. This
option is also available if more than one Configuration Profile is selected in
the tree (or table).
Refresh:
Retrieves the latest list of Versions for the Configuration Profile. This can
change if another User commits a version.
Compare:
If you select two Configuration Profiles, the Compare option
appears on the right-click context menu. The Configuration Profiles are loaded
into the Profile Editor tab if they are not already loaded.
A new Compare and Merge tab is opened that shows the
differences, if any, between the two selected Configuration Profiles. For more
details, see the Comparing and Merging
Configurations topic.
Configuration Profiles owned by another User
When a User selects a Configuration Profile node that they do not own, only the
Edit, Create via Copy, Export,
Refresh, and Compare options are enabled.
Important Note: A User can load another User's Configuration Profile,
but can not commit a new version of it. The User can make local changes to the
Configuration Profile, and then create a new Configuration Profile from the Profile
Editor tab that includes the local changes. You can do this using the Create
Configuration menu option on the top-level node. This is similar to the Create
via Copy option but differs in that it includes any local changes in the newly created
Configuration Profile.
Super User Access
The Super User can access all functionality on this node for all Users.
Both the Super User and the owner User can modify a Configuration Profile simultaneously
when they both make changes locally. However, the commits are synchronized so that
if a commit occurs after you load the Configuration Profile, you are warned when attempting
to commit a new Version. You can then choose to continue and overwrite the last
User's changes.
Alternatively, you can cancel the commit operation, create a new
Configuration Profile from your locally modified Configuration Profile, load the new
Version created by the other User, compare both Configuration Profiles, and then
merge the changes before committing a new Version. You can use the
Refresh menu option on the Configuration Profile
node to retrieve the latest list of Versions.
|