Manage the Profiles search operation 




Use Profiles configuration settings to control how the search operation displays search results.

Before you begin


To edit configuration files, use the IBM® WebSphere® Application Server wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.

Procedure


To configure Profiles search...

  1. From the dmgr host:

      cd $DMGR_PROFILE/bin
      ./wsadmin.sh -jython
      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, pick the node where the file is stored.

  2. Check out the Profiles configuration files:

      @nowiki@6where:

      • <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 WAS 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()

      For example:

      • AIX or Linux:

          ProfilesConfigService.checkOutConfig("/opt/prof/temp","foo01Cell01")

      • Microsoft Windows:

          ProfilesConfigService.checkOutConfig("c:/prof/temp","foo01Cell01")

  • To configure the Profiles search operation, use the following command:
    Property Description
    search.maxRowsToReturn Determines the maximum number of Profiles database rows returned by a name search operation.
    This property takes an integer value. The default value is 250. You can increase the number, but do not specify a number larger than 500. Doing so causes search operations to fail entirely. Do not specify 0 unless you want no results to be returned.
    The keyword and directory search operations do not have this limit.
    search.pageSize Determines the number of returned rows to place on a results page.

    This property takes an integer value. The default value is 10.
    search.firstNameSearchEnabled Determines if search by first name only is enabled. By default, this setting is set to false.

    This property takes a Boolean value.

    Note: Enable this setting negatively impacts the performance of the Search by > Name function available in the Profiles user interface.
    nameOrdering.enabled When this property is set to true, names must be entered as (FirstName LastName) or (LastName, FirstName). By default, it is set to false.

    This property takes a Boolean value.

  • To specify the default sorting key to use for displaying search results, edit properties in the profiles-config.xml file manually as follows.

    1. Open the profiles-config.xml file in a text editor.

    2. Update the following properties as needed.

        sortNameSearchResultsBy

        • Determines what sorting key to use for Profiles name search results. This property is also applied to the search results that display when a tag is clicked in a profile overview page. It does not affect the results generated by clicking a tag in a directory search.
          The valid values for the default attribute are:

          • displayName. Lists name search results in order of user display name.

          • last_name. Lists name search results in order of user last name.

          For example:

          <sortNameSearchResultsBy default="displayName" />

        sortIndexSearchResultsBy

        • Determines what sorting key to use for Profiles keyword and advanced search results.

          The valid values for the default attribute are:

          • relevance. Lists keyword and advanced search results in order of relevance.

          • displayName. Lists keyword and advanced search results in order of user display name.

          • last_name. Lists keyword and advanced search results in order of user last name.

          For example:

          <sortIndexSearchResultsBy default="relevance" />

    3. Save your changes and then close the profiles-config.xml file.

  • After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply property changes in Profiles for information about how to save and apply your changes.



    Parent topic

    Administer Profiles
    Related concepts
    Customize Profiles search

    Related tasks
    Apply property changes in Profiles



    December 14, 2011 11:04:52 AM
       

     

    Dec 14, 2011 11:04:52 AM Dev fix to SPR#WDWU8MYA9C set max to 500, so updating doc to reflect t... 2 Dec 9, 2011 4:58:05 PM Added minimum/maximum value info to the description of the search.maxR... 1

    });