Administer ProfilesProfiles provides two types of administrative capabilities: configuration settings and administrative commands. You change configuration settings and execute administrative commands by running scripts from the wsadmin command line.
Jython Scripts run from a wsadmin command line are used to configure and to administer Profiles. These scripts use the AdminConfig object available in IBM WAS Admin (wsadmin) to interact with the configuration repository.
You can update the Profiles environment in two ways:
Modify these settings to control various configurable applications within Profiles. When you make configuration changes, you use scripts to check out the Profiles configuration file, profiles-config.xml, make changes, and then check the file back in. A server restart is required for your changes to take effect.
Use these commands to control various aspects of the Profiles environment. Administrative commands do not require a server restart to take effect.
Running Profiles administrative commands
Scripts are used to administer the Profiles application. These scripts use the AdminConfig object available in IBM WAS wsadmin client to interact with the Profiles server.
Change Profiles configuration property values
Configuration settings control how and when various Profiles operations take place. You can edit the settings to change the ways that profiles behave.
Developing custom Tivoli Directory Integrator assembly lines for Profiles
You can use IBM Tivoli Directory Integrator connectors to develop custom assembly-line scripts when you need to provide a specific type of function.
You can enable the active content filter to prevent users from embedding malicious content in text input fields in Profiles. You can also use administrative commands to update or remove inappropriate information in fields to which you do not have owner access.
Configure features by profile type
You can configure certain features in Profiles according to profile type.
Configure widgets in Profiles
To configure existing widgets or to make custom widgets available for use in Profiles, you modify settings in the widgets-config.xml file.
You can modify settings in the profiles-config.xml file to configure the full report-to and object caches for Profiles. Use Profiles administrative commands when you want to enable, disable, or reload the full report-to chain cache.
Manage the Profiles search operation
Use Profiles configuration settings to control how the search operation displays search results.
Monitoring statistics and metrics for Profiles
Use the statistics and metrics gathering capabilities of Profiles to monitor operations and product usage.
Configure the vCard export application for Profiles
Configure settings in the profiles-config.xml file to specify the character set encoding options used to export vCards. The table below lists the character set encoding options that work best.
Making photos cachable in secure environments
If your Profiles deployment is configured to prevent profile data from being accessible to readers, you can opt to make just user photos cachable.
Enable the use of pronunciation files in an HTTPS environment
Ensure that Profiles users can save and play pronunciation files in an HTTPS environment by defining a rule in the IBM HTTP Server's configuration file.
Manage the Profiles event log
Use Profiles administrative commands to manage the Profiles event log.
Configure advanced settings in Profiles
Configure advanced settings in Profiles by adding information to the <properties> element in the profile-config.xml file.
Parent topicAdminister IBM Connections
Customize the Profiles business card
Integrate the Profiles business card