Server Design Search tab
You must enter the criteria of the search that is directly run on the server.
- Search string
- Enter the character string that you want to search for. This string
represents the whole or partial name of the element that the search
is run on. This element is selected in the Limit to field. You can use the following wildcard characters:
- An asterisk matches one or more characters of any value.
- A question mark matches a single character of any value.
- Case sensitive
- Check this box if the character string to search for is to match the case that is entered in the Search string field.
- Search for
- Select the entities that you want to search for.
- Search in
- You can limit the search scope by selecting one or more projects. For a server search, this
selection significantly reduces the search running time and limits the traffic between the client
and the server. For a local or server design search, this field displays the hierarchy of the design projects as it is indicated in the deign compilation path. You can select projects in different ways by clicking the Checking mode buttons:
- One or more separate projects in the hierarchy. If you select a project, its hierarchy is not taken into account.
- A project with its upper hierarchy.
- A project with its lower hierarchy.
- All the projects of the hierarchy.
For a server artifact search, the list of the projects in this field includes all the projects of the selected streams. The projects that contain the design files and the projects that contain the generated files are displayed according to their alphabetical order, without any hierarchical level. Only the projects that you select explicitly are browsed upon the search.
Note: For server searches, if you select All streams in Server scope, then the list of the projects is irrelevant and only the line Search in all projects is available.
- Limit to
- You indicate where the string that is entered in the Search
string field is to be searched for. You can select only
one item:
- The instance name.
- The project where the instances are searched for.
- The package where the instances are searched for.
- The keywords that are entered in the instance Keywords tab.Note: The implicit keywords are also recognized upon a local design search in the Pacbase facet. So, if the string is present in the label of an instance, this instance will also be retrieved by the search.
- The keywords that are entered in the instance Keywords tab,
and their synonyms that are specified in the thesaurus. If you select
this item, you must enter the entire search string and select a location
(because a thesaurus is defined at the location level).Note: The implicit keywords are also recognized upon a local design search in the Pacbase facet. So, if the string is present in the label of an instance, this instance will also be retrieved by the search.
- The instance label.
- Location Scope
- You can limit the search to one location only. To do so, select the
Location radio button. A list that displays all the local locations becomes
available.
If the location where you want to search for instances does not locally exist, you enter its name (as on the server) in the input field. The search is then run on the instances that are present in this location on the server.
- Diagram scope
- The
diagram represents the hierarchy of the projects that are contained in the location. It is defined
in the design build path wizard. You open this wizard by right-clicking a location in the
Design Explorer view and selecting Properties. The
notions of application domain and level (position in the diagram) are associated with each project.
You can limit the search scope to some Domain and
Level values that exist in the build path.
A domain groups the projects according to application criteria. You can indicate one or more existing domains.
In a tree organization, the level implicitly corresponds to the position of a project in the tree. The root node has a level 0. The child nodes of the root have a level 1. The final leaves of the tree have the highest levels.
In a layer organization, the level is associated with each layer. The layer that groups the projects that are required by all the other projects has a level 0. The layer that groups the projects that are not required by any other project has the highest level.
You can enter a level in the input field and select a position in relation to this level (>, >=, =, <, or <=).
- Server scope
- You can select a stream to limit the search scope.
A stream is the equivalent of a work session. It is a repository object that is created in the Rational Team Concert™ server to integrate the work that is done in workspaces.