Changing 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.

Before you begin

To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.

About this task

Configure Profiles using scripts accessed with the wsadmin client. These scripts use the AdminConfig object available in the IBM® WebSphere® Application Server wsadmin client to interact with the Profiles configuration file. Changes to configuration settings require node synchronization and a restart of the Profiles server before they take effect.

Note: There are no Profiles application administrative tools for adding or removing a user's profile. If you want to add or remove a profile for a person, you must add or remove that person's entry from the corporate LDAP directory system. Use that directory's native tools to create and delete user entries. When you perform standard synchronization tasks on the Profiles database, the profiles are updated. If you add a new user to the LDAP directory, a profile is created for that user. If you remove a user entry from the LDAP directory, that user's profile is removed. See Synchronizing user data between Profiles and the LDAP directory for more details.

To change Profiles configuration settings, complete the following steps:

Procedure

Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
```
app_server_root\profiles\dm_profile_root\bin
```
where app_server_root is the WebSphere Application Server installation directory and dm_profile_root is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly.
Start the Profiles Jython script interpreter.
1. Enter the following command to access the Profiles configuration files:
  execfile("profilesAdmin.py") If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
2. Enter the following command to check out the Profiles configuration files:
  ProfilesConfigService.checkOutConfig("working_directory", "cell_name" where:
  - working_directory is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes (/) to separate directories in the file path, regardless of your operating system.
    Note: In order for the command to complete successfully, the directory must grant write permissions if you are using one of the following operating systems:
    
    AIX
    
    Linux
  - cell_name is the name of the WebSphere Application Server cell hosting the Profiles application. This argument is required. It is also case-sensitive. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor: print AdminControl.getCell()
  For example:
  - AIX or Linux:
```
ProfilesConfigService.checkOutConfig("/opt/prof/temp","foo01Cell01")
```
  - Microsoft Windows:
```
ProfilesConfigService.checkOutConfig("c:/prof/temp","foo01Cell01")
```
To change a Profiles configuration setting, use the following command:
ProfilesConfigService.updateConfig("property", "value")
where:
- property is one of the editable Profiles configuration properties.
- value is the new value with which you want to set that property.
For example, the following code disables the display of organizational information.
```
ProfilesConfigService.updateConfig("organizationalStructure.enabled","false")
```
See Profiles configuration properties for a complete list of editable properties.
Optional: Repeat the previous step once for each property setting you want to change.

What to do next

You must check the configuration files back in after making changes, and they must be checked in during the same wsadmin session in which they were checked out for the changes to take effect. See Applying property changes for details.