The following sections explain how to search an locate an asset in WSO2 G-Reg Store.
Table of Contents maxLevel 3
...
You can navigate to the G-Reg Store Web user interface to discover and use various asset types as described below.
Info |
---|
For information on accessing the G-Reg Store using a remote instance, see Enabling Remote Access for Governance Center. |
URL format | http://<G-REG_HOST>:<G-REG_HTTP_PORT>/store https://<G-REG_HOST>:<G-REG_HTTPS_PORT>/store |
---|---|
Description | By default, |
Example | http://localhost:9763/store https://localhost:9443/store |
You view the home page for anonymous users as shown below.
...
The system administrator will be able to log in using admin
as the username and password. However, other users will have to first register with G-Reg Store before being able to log in. Follow the instructions below to register with G-Reg Store.
Navigate to the G-Reg Store. For instructions, see Navigating to G-Reg Store.
- Click the following Register button in the upper right corner of the screen.
You view the following screen.
- Enter a preferred username and password.
- Enter the password again for Confirm Password.
- Enter the email address.
- Enter the first and last names.
- Click REGISTER.
- Click the Sign in link in the following screen which you view once the new user is successfully created.
- Sign in using the credentials of the user you created. For instructions, see steps 3-4 in Logging into G-Reg Store.
...
Follow the instructions below to log in to WSO2 G-Reg Store.
Navigate to the G-Reg Store. For instructions, see Navigating to G-Reg Store.
- Click the following Sign in button in the upper right corner of the screen.
Enter your username and password in the next screen as shown below.
Tip If you do not have credentials to log in yet or if you did not register, you may temporarily use the default admin/admin credentials.
- Click SIGN IN. The home page will appear as shown below.
Expand | ||
---|---|---|
| ||
Follow the instructions below to log out of WSO2 G-Reg Store.
|
Searching for an asset
Once you access the G-Reg Store, you can search for assets using the provided search field as shown below.
Note |
---|
|
...
title | Using keywords to search |
---|
WSO2 G-Reg Store supports the following advanced search operators, for you to use as keywords or symbols, to find what you are looking for quickly and accurately in the search operation. You can view a summary of these by clicking the info icon next to the search filed as shown below.
...
name
:"Ordering Service.wadl"
Info |
---|
Use double quotes within the search query, if you are specifying the name of an asset, which includes spaces in between its words. |
...
Buymore
Info |
---|
If you type text without a keyword in the search field, the search query interprets it as you want to retrieve an asset that contains the word you enter in its name. For an example, typing "BuyMore" is similar to the following search query: |
...
-
mediaType:
wsdl -
mediaType:
soap-service
...
version:
1.0.0
...
-
tags:
mac -
tags:
new-Engineering
Note |
---|
The search query for tags does not allow you to use spaces in between its words. Therefore, to search using a tag that includes spaces (e.g. "new Engineering"), use the dash sign in the search query. |
...
Searches for assets with content as preferred. You view assets which contain the word you enter in its content. Other than that, you can search sentences by passing the value within quotes.
content:
uber
Info |
---|
For assets with metadata-type RXTs, which you create (e.g. SOAP and REST Services etc.), use words found in any field name or value in the RXT file of the asset as search parameters in the search query. For information on the field names and values, see any section in the Viewing Information of an Asset . |
...
content
:"Adding the WSDL file"
Info |
---|
For assets with content-type RXTs (e.g. WSDLs, WADLs, Swaggers etc.), use words found in the source file of the asset as search parameters in the search query. For information on the source file, see the Content section in Viewing Information of an Asset. |
...
-
associationType:
depends -
associationType:
security
...
...
category:
Engineeringcategory:
Marketing
...
Searches for assets by the given RXT field value. You view assets which have the value as specified of the given RXT field name. For information on table and field names of a Configurable Governance Artifact (RXT) file, see Governance Artifacts Configuration Model Elements.
...
overview_category:Engineering
Info You do not need to specify the
<RXT_TABLE_NAME>
(i.e.overview_
) when searching for values in fields of theoverview
table (e.g.category
), since it gets automatically appended in the search query. Hence, you can type the above search query as category:Engineering.- interface_transports:https
- security_authenticationType:none
...
name:
echo version:
1.0.0
Expand | ||
---|---|---|
| ||
WSO2 G-Reg is capable of tracking the search history in the G-Reg Store search functionality. When you search for assets in the G-Reg Store, those search queries will be automatically stored against your user role. Hence, you will not loose search history results even when the session is destroyed. Also, WSO2 G-Reg maintains search history per asset type. E.g. search history in REST Services and search history in SOAP Services will be different. When you start typing a search query in the provided search field, you view a list with matching search history queries as shown in the example below. This allows you to reuse the same query without completing typing it as shown below. Search history tracking configurationsFollow the steps below to configure the search history tracking feature by changing the properties defined in the
|
Expand | ||
---|---|---|
| ||
Once you create an asset by assigning terms to it, it will be available in the WSO2 G-Reg Store. You can navigate through the top drop-down hierarchy, to select the asset as shown below. For example, once you select Line Of Business 3 and Department15 as shown below, it lists down all the assets that belong to Line Of Business 3/Department15. |
Expand | ||
---|---|---|
| ||
Once you add categories to an asset, you can use categorization to search for a SOAP Service in the G-Reg Store by its category as shown below. |
...
...
The following sections explain how to search an locate an asset in WSO2 G-Reg Store.
Table of Contents maxLevel 3
Anchor Navigating to G-Reg Store Navigating to G-Reg Store
Navigating to G-Reg Store
Navigating to G-Reg Store | |
Navigating to G-Reg Store |
You can navigate to the G-Reg Store Web user interface to discover and use various asset types as described below.
Info |
---|
For information on accessing the G-Reg Store using a remote instance, see Enabling Remote Access for Governance Center. |
URL format | http://<G-REG_HOST>:<G-REG_HTTP_PORT>/store https://<G-REG_HOST>:<G-REG_HTTPS_PORT>/store |
---|---|
Description | By default, |
Example | http://localhost:9763/store https://localhost:9443/store |
You view the home page for anonymous users as shown below.
Anchor Registering with G-Reg Store Registering with G-Reg Store
Registering with G-Reg Store
Registering with G-Reg Store | |
Registering with G-Reg Store |
The system administrator will be able to log in using admin
as the username and password. However, other users will have to first register with G-Reg Store before being able to log in. Follow the instructions below to register with G-Reg Store.
Navigate to the G-Reg Store. For instructions, see Navigating to G-Reg Store.
- Click the following Register button in the upper right corner of the screen.
You view the following screen.
- Enter a preferred username and password.
- Enter the password again for Confirm Password.
- Enter the email address.
- Enter the first and last names.
- Click REGISTER.
- Click the Sign in link in the following screen which you view once the new user is successfully created.
- Sign in using the credentials of the user you created. For instructions, see steps 3-4 in Logging into G-Reg Store.
Anchor | ||||
---|---|---|---|---|
|
Follow the instructions below to log in to WSO2 G-Reg Store.
Navigate to the G-Reg Store. For instructions, see Navigating to G-Reg Store.
- Click the following Sign in button in the upper right corner of the screen.
Enter your username and password in the next screen as shown below.
Tip If you do not have credentials to log in yet or if you did not register, you may temporarily use the default admin/admin credentials.
- Click SIGN IN. The home page will appear as shown below.
Expand | ||
---|---|---|
| ||
Follow the instructions below to log out of WSO2 G-Reg Store.
|
Searching for an asset
Once you access the G-Reg Store, you can search for assets using the provided search field as shown below.
Note |
---|
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WSO2 G-Reg Store supports the following advanced search operators, for you to use as keywords or symbols, to find what you are looking for quickly and accurately in the search operation. You can view a summary of these by clicking the info icon next to the search filed as shown below.
|
Expand | ||
---|---|---|
| ||
WSO2 G-Reg is capable of tracking the search history in the G-Reg Store search functionality. When you search for assets in the G-Reg Store, those search queries will be automatically stored against your user role. Hence, you will not loose search history results even when the session is destroyed. Also, WSO2 G-Reg maintains search history per asset type. E.g. search history in REST Services and search history in SOAP Services will be different. When you start typing a search query in the provided search field, you view a list with matching search history queries as shown in the example below. This allows you to reuse the same query without completing typing it as shown below. Search history tracking configurationsFollow the steps below to configure the search history tracking feature by changing the properties defined in the
|
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Once you add filters to an asset, you can use those filters to search for an asset in the G-Reg Store as shown below. Navigate through the Taxonomy hierarchy nodes and click Add Filter to create the filter at a preferred level. In the following example, Teams -> New Jersey -> The Rock Stars has been selected.
You can add more filters from the same taxonomy by clicking on the Add Filter button as shown below.
Also, you can add multiple filters from different taxonomies as shown below.
|
Expand | ||
---|---|---|
| ||
Once you add categories as search refinements to an asset, you can use them to search for a SOAP Service in the G-Reg Store by its category as shown below. |
Anchor | ||||
---|---|---|---|---|
|
For an example, you can search for version 1.0.0 of the BuyMoreBillCalculateRESTAPI asset (i.e. deployed when you execute the Quick Start Guide sample), by typing the following text in the provided search field as shown below: name:BuyMoreBillCalculateRESTAPI version:1.0.0
Changing the default search
In G-Reg versions 5.1.0 and 5.2.0, the default search returned results only related to the name field of the RXT. However, in G-Reg 5.3.0, you can change this default search behavior in WSO2 Governance Registry Store to give any query pattern for the default search as required. Follow the steps below to configure the default search.
Note |
---|
This default search query will be given more priority than the taxonomy and categorization search. |
- Navigate to the
<G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/store.json
file. Change the value of the following
defaultSearch
template to the query you need to execute as the default search.Code Block language js "search": { "defaultSearchTemplate":"name=*$input* OR *$input*" }
For example, if you need the default search query to return results, which are related to the name field or lcName field of the RXT, you can change the value as follows:
Code Block language js "search": { "defaultSearchTemplate":"name=*$input* OR lcName=*$input*" }