This topic applies only to the IBM Business Process Manager Advanced configuration.

Enabling searches for user registries without wildcards

If your user registry is set up to not use wildcards, you must complete additional configuration steps so that searches work properly in Process Portal and for widgets that search the user registry.

Before you begin

Before you complete this task, you must have completed the following tasks:

Enable application security and administrative security. See Enabling security for dashboards.
Check that your user ID is registered in the user registry for your product.

About this task

By default, when a Process Portal user searches for users or groups by typing one or more characters, Process Portal automatically adds wildcard characters. For example, if the user registry is an LDAP server and the user types smit, Process Portal converts this into a *smit* query so that the return includes names like Smith, Smithers, and Psmith. However, if you do not want the automatic wildcards because, for example, your user registry does not permit them, you can disable this functionality.

To turn off the automatic wildcard searches for your environment, complete the following steps.

Procedure

For a stand-alone server, complete the following steps:
1. Update the profile_root\BusinessSpace\node_name\server_name\mm.runtime.prof\config\ConfigService.properties configuration file with com.ibm.mashups.user.stripWildcards=true.
2. Run the updatePropertyConfig command in the wsadmin environment of the profile:
  The following example uses Jython:
  
  AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name -propertyFileName "profile_root\BusinessSpace\node_name\server_name\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"]')
  
  AdminConfig.save()
  
  Important: For Windows, the value for the propertyFileName parameter must be the full path to the file, and all backslashes must be double, for example:AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name -propertyFileName "profile_root\\BusinessSpace\\node_name\\server_name\\mm.runtime.prof\\config\\ConfigService.properties" -prefix "Mashups_"]').
  
  The following example uses Jacl:
  
  $AdminTask updatePropertyConfig {-serverName server_name -nodeName node_name -propertyFileName "profile_root\BusinessSpace\node_name\server_name\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"}
  
  $AdminConfig save
3. Restart the server.
For a cluster, complete the following steps:
1. Update the deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\config\ConfigService.properties configuration file with com.ibm.mashups.user.stripWildcards=true.
2. From the deployment manager, run the updatePropertyConfig command in the wsadmin environment of the profile:
  The following example uses Jython:
  
  AdminTask.updatePropertyConfig('[-clusterName cluster_name -propertyFileName "deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"]')
  
  AdminConfig.save()
  
  The following example uses Jacl:
  
  $AdminTask updatePropertyConfig {-clusterName cluster_name -propertyFileName "deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"}
  
  $AdminConfig save
3. Restart the deployment manager.