Customizing the Profiles user interfaceAdded by IBM | Edited by IBM on March 15, 2012 | Version 3 (Show original)
|Specify which attributes should display in Profiles based on the needs of your organization.
Specify which attributes should display in Profiles based on the needs of your organization.
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
Once you have decided which of the Profiles attributes you would like to display and which ones you want to allow users to edit, you are ready to configure the attributes, using the wsadmin client scripts for customizing Profiles. These steps provide an overview.
A configuration change requires synchronization of the Profiles node and a restart of the Profiles server to become effective. The configuration changes being made are only for the node specified when you perform the checkOutConfig
command. If you want to make those changes to other nodes, then you need to repeat this process for the other nodes.
To change Profiles configuration settings to customize the user interface, complete the following steps:
Parent topic: Customizing Profiles
Applying property changes in Profiles
Updating profile entries
Retrieving the Profiles service document
Retrieving the Profiles Administration API service document
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
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.
- Use the wsadmin client to access and check out the Profiles configuration files.
- 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.
- Enter the following command to check out the Profiles configuration files:
- <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, even if you are using the Microsoft Windows operating system.
Note: AIX and Linux only: The directory must grant write permissions or the command does not complete successfully.
- <cell_name> is the name of the WebSphere Application Server cell hosting the Profiles application. This argument is required. It is also case-sensitive, so type it with care. 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()
- AIX or Linux:
- Microsoft Windows:
- Although you should try to avoid directly editing XML configuration files, and use appropriate wsadmin commands to modify applications, this is one area where commands are not available. Locate the Profiles configuration file, profiles-config.xml, in the local working directory specified in the checkOutConfig command. The Profiles configuration file contains the various configuration settings for the Profiles application. Here is the relevant section for customizing the Profiles user interface:
Although you cannot control the order of appearance of profile sections such as Contact Information or Associated Information, the order in which individual fields appear in the user interface reflects their order in the configuration file. For example, if you want the ipTelephoneNumbertelephoneNumber
field to appear before the telephoneNumber
field, simply change the order of the fields in the file.
- Modify the files, following the steps (detailed in the topics that follow) for choosing attributes and specifying which are editable. Many of the attributes are already listed in the configuration file, so you simply need to comment out what you don't want, or remove the comment statement from attributes you do want. If an attribute you want is not listed, add it to this file.
- After making changes, you must check the configuration files back in, and you must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes in Profiles for information about how to save and apply your changes.
Choose from among the predefined Profiles attributes to identify the job, contact, and associated information attributes that are included in the Profiles user interface.
Specifying external labels for attributes
Connections, you can apply custom labels stored in an external resource bundle to any attribute, editable attribute, or custom extension attribute.
Specifying attributes that can be edited
Specify which attributes in the Profiles user interface can be edited. Attributes that can be edited display on the Edit My Profile
Specifying read-only attributes
When you want to specify an attribute that cannot be edited by users, you enclose the attribute in an <attribute> element.
Customizing login attributes
By default, Profiles looks at the login table and the three login attributes defined below to perform. To improve performance, you can comment out the attributes that are not used in your environment.