In all sectors, team members can now use more and more destination-based, cloud-based tools such as google driver, salesforce, github and so on. These tools are more focused and easier to use than ever before. This provides a new form of large and small team collaboration, faster execution speed and enhance productivity. The proliferation of content created tremendous value, but also created a new opportunity: to unify all the information in one place and makes it possible to easily search for a single opportunity in the search box. Elastic Workplace Search make this possible, and now easier than ever before.
In our work, we sometimes I want to search the article contains a number of keywords, but we're not sure what this article is placed or where to store the documents in. This article may be in a dropbox, google drive, salesforce. Office 365, confluence, gira, or your own custom file storage place. We have any good way to help us search for and locate documents quickly we want it?
The answer is Elastic Workplace Search . It is a personalized, centralized and secure search experience organized a complete solution. It can help us to quickly search all the tools in our work are used in the document. Elastic introduced a lot of sophisticated data connector. This includes Dropbox, Salesforce, G Suite, JIRA , Confluence and the like.
Elastic Workplace Search makes finding information work is not only effective, but also very pleasant. With its highly beautiful, user-friendly UI and search-box correlation with. When searching, please take advantage of useful features, such as document preview and advanced keyword detection ( "document" = .pdf, .doc, .xls, etc.). With the search function, the office everyone finally have their own personal assistant.
On the right side of the chart, we can see a preview of the document.
Keep it simple, simple
Elastic Workplace Search consumer-level enterprise search solution . It provides easy-to-use tool for all throughout the organization use, powerful search. For your daily work, this is a fast, scalable and relevant search bar.
In Elasticsearch reliable basis for relevance and scalability, we designed a search experience that only requires you to search for ways to talk with colleagues, you can quickly find the content of the document or answer required. Without configuring complex applications, traversing complex interfaces or learn any strange convention: Elastic Workplace Search understand your intentions and keep you focused on the task at hand.
Advanced keyword detection
Bid farewell to the days of anxiety, where multiple browser windows containing hundreds of open tabs. Search for all documents, pull request, issue tickets, contracts, spreadsheets - no matter where they are, no matter where you are, can get the job done through a single, coherent gateway .
Connector
Elastic Workplace Search comes with a cloud connector application that lets you get started in just minutes. For the first beta version, we highlight today's modern organizations most commonly used cloud applications:
- Google Drive : search for all documents, forms, slides and stored files
- GitHub : Receive all questions and requests extract
- Salesforce : synchronization accounts, contacts, leads, and opportunities
- Dropbox : index of all images, static files and documents
- Custom connectors frame: synchronization data from any source, such as internal applications, analysis engine, or a dedicated communication channel knowledge
Correlation
Elastic Workplace Search offers privacy groups and adjustable search relevancy, so that the right people get the right things. Each team member is assigned to a group: engineering, sales, marketing, design, product, leadership (most appropriate for your organization), and calibrate the relevance of its resources according to their specific needs:
, Salesforce, the importance of adjusting the GitHub for your sales team Dropbox engineering team for the design team; any appropriate. Use fine-grained access control and group assignments, you can instruct individuals and groups will find the contents of the safe. What will not find ...
Elastic Workplace Search includes you would expect from Elastic solve all the features of the program was: simple data index, seamless scalability and ultra-fast speed, and highly relevant algorithms, search history, auto-complete, linguistic analysis, typo tolerance and many more. All of these have been well documented Elastic, community-centered expert support.
Ready to start yet?
Hands
In this chapter, we show how to hands-on Elastic Workplace Search charm!
Install Java
On your computer you need to install Java 8 or the Java 11 . For the Ubuntu operating system developers, you can refer to my previous article " How to install the Java on Ubuntu ."
Installation Elasticsearch and Kibana
For developers without installing Elastic Stack's, you can read my previous article " Elastic: Rookie Start Guide " and installation Elasticsearch Kibana. You can also deploy a version of Elasticsearch Docker in the following way:
According to Workplace Search installation requirements, we need to buy elasticsearch Platinum License , or start a 30-day trial. In today's test, we start the 30-day trial. We open Kibana:
Next, we need to start Elasticsearch security mechanisms. We modify the config / elasticsearch.yml file in the root directory of Elasticsearch. We need to add:
xpack.security.enabled: trueTo elasticsearch.yml file. After modification, etc., let's start Elasticsearch in a terminal in which:
./bin/elasticsearchOnce Elasticsearch start, we have another in a terminal, enter the following command and produce a random password elastic users:
$ ./bin/elasticsearch-setup-passwords auto
Initiating the setup of passwords for reserved users elastic,apm_system,kibana,logstash_system,beats_system,remote_monitoring_user.
The passwords will be randomly generated and printed to the console.
Please confirm that you would like to continue [y/N]y
Changed password for user apm_system
PASSWORD apm_system = ZrYWbqpBBfSJTdz3ekud
Changed password for user kibana
PASSWORD kibana = 99aB61B6N1mJBDkknZfB
Changed password for user logstash_system
PASSWORD logstash_system = rkfV7w8bMNI0gvPHOktR
Changed password for user beats_system
PASSWORD beats_system = lYFRW1Dum7xEUATfZBnA
Changed password for user remote_monitoring_user
PASSWORD remote_monitoring_user = KgfupKJHQlFSl8SSR5ZR
Changed password for user elastic
PASSWORD elastic = izdhd03fJI2c1xsVa8HjThese passwords we need to record, for our future use. In the elastic user here is a super user. In this experiment, we use this user. We also need to do the appropriate configuration in Kibana in the past allows us to log on Kibana. Specifically how to do, see my previous article " elasticsearch: Set Elastic account security ."
安装Elastic Workplace Search
You can address Workplace Search download the latest software. We can also use the following command to install:
wget https://download.elastic.co/downloads/enterprisesearch/enterprise-search-7.6.0.tar.gzElastic Stack according to installation requirements, we need to install and consistent Elasticsearch version Workplace Search software. In the above we are installing a version of version 7.6, Elasticsearch version also corresponds to our latest 7.6 version. Etc. We Workplace Once downloaded, we use the following command to install:
tar xzf enterprise-search-7.6.0.tar.gz
cd enterprise-search-7.6.0We now configure the config / enterprise-search.yml file. With our favorite editor to open the file and add the following contents:
elasticsearch.host: [ELASTICSEARCH_URL]
ent_search.auth.source: standard
elasticsearch.username: elastic
elasticsearch.password: [ELASTIC_USER_PASSWORD]
allow_es_settings_modification: trueWe remember with elastic user password above steps in place of the above [ELASTIC_USER_PASSWORD] . We also need to use on our elasticsearch actual address instead of [ELASTICSEARCH_URL], such as http://127.0.0.1:9200. In case of default, http: //127.0.0.1: 9200 is the default value, we do not need to make any changes.
启动 Elastic Workplace search
In the above we have successfully installed Elastic Stack and Workplace Search. Next, we started Workplace Search. Here are two ways to start:
1) define your preferred password on the command line:
ENT_SEARCH_DEFAULT_PASSWORD=passwordexample bin/enterprise-search2) run directly enterprice search, and we need to get my password:
bin/enterprise-searchDuring our first run, we can see the following output:
#########################################################
*** Default user credentials have been setup. These are only printed once, so please ensure they are recorded. ***
username: enterprise_search
password: rsrcto4ktvweb7p5
#########################################################
We can see enterprice-search will generate a username and password. Just as described above, we need to record the user name and password, since it is only displayed once. Once lost, never get a chance.
We can also see some of the following information:
#########################################################
Success! Elastic Workplace Search is starting successfully.
In a few moments, you'll be able to login at the following address:
* URL: http://localhost:3002
* If this is your first time starting Workplace Search, check the console output above for your user authentication credentials.
* Visit the documentation: https://swiftype.com/documentation/enterprise-search
Secret session key has been generated.
Set the key in your config file to persist user sessions through process restarts:
secret_session_key: b0975084081fe37f5a01b5eeb548b5ba7c13d27ecca5ac5f723e066214c2ca44de041ad819ac19e11b42f3d612447e93f3b8f29d67de0fd6d35aab5ac5098af2
No secret management encryption keys were provided.
Your secrets will be stored unencrypted.
You can use the following generated encryption key in your config file to store new encrypted secrets:
secret_management.encryption_keys: [5b83691889bbbfc4965d2952f9d24ef225c5d48a134386c6e914b82f76811285]
#########################################################
In the above we can see the enterprise-search operation on the 3002 address. We can see two key above:
secret_session_key: c62a8a82d8340fec1ba706ee81740be8483da30a94dc43468697880b7b9e87da81de81d307ebde23a1906695dbfa7e2dc4208ab17df8cb97d2cb2fa15bdd131b
secret_management.encryption_keys: [fff3ab3a8ba31911250d8d17014e367483d1e08570e9e1e6ae0f048d93aad9ae]
We need to fill to the top of the key config / Enterprise-search.yml file to ensure that users of enterprise-search session after the restart .
vi config/enterprise-search.yml
Once we have finished modifying the above configuration, we re-start our enterprise-search, we can see the following output:
#########################################################
Success! Elastic Workplace Search is starting successfully.
In a few moments, you'll be able to login at the following address:
* URL: http://localhost:3002
* If this is your first time starting Workplace Search, check the console output above for your user authentication credentials.
* Visit the documentation: https://swiftype.com/documentation/enterprise-search
#########################################################Above show our Elastic Workplace Search has been successfully launched and runs to 3002 port address.
When first started running, we can see some output as follows:
Starting the following Elastic Enterprise Search stack components:
- An application server, as well as background worker threads
- A pool of connectors
- A filebeat instance for indexing logs
forego | starting app-server.1 on port 5000
forego | starting filebeat.1 on port 5100
forego | starting connectors.1 on port 5300 We can see from the above output came out: He started it and an application server and a filebeat some examples of connectors.
We in the address bar of your browser, enter the address localhost: 3002, we can see the following screen:
As shown above, it shows the current operating status intact. Trial our Elasticsearch there 29 days trial period. We click on " the Continue to the Login ":
We preserved before the user name and password into the dialog box, and click on " the Log in " button:
Hooray! We finally saw our first Workplace Search the first screen. This is the default screen of our Workplace Search. From here we can add Source, invite users and customize your experience.
Let's start with adding Source started!
Adding a Data Source
In this section, we add a dropbox source. Specific operational procedures, see " Dropbox Connector "
We first went to https://www.dropbox.com/developers/apps add an application:
We click on " the Create App ":
Click on " the Create App " button:
We note the above App key and App secret, to be used when the following is added source. If we want our own Brand of the application, we can click on the "Branding" tab to configure our own application icon.
In the Workplace Search the default screen, we click " the Add A Source ":
We can see the following picture:
In the above, we can see some Connectors currently in the Workplace Search already exist. In the above, there is some work we are very familiar tools. In today's experiment, let's add a familiar Source: dropbox. We click on the Dropbox picture:
We click on the " the Configure Dropbox ." We enter their ClientId and Secret:
Then we can enter the following screen:
Click on the " Connect Dropbox ", we can connect our Dropbox of:
Let us then click on " Connect Dropbox ":
We fill our Dropbox username and password:
We click on " the Continue " button:
We click on " the Allow " button:
We have successfully shown above the Dropbox connected.
We select the Search application:
We need to wait for some time, and so on Workplace put all the documents indexed. Once this process is complete, we can begin looking for:
In the above, we can see an example of a smart filter. When we enter the jpg, it will automatically help us to add a filter called a jpg.
We in the input box, enter "Getting started pdf", it also gives us generate a pdf of the filter. Getting Started.pdf we click on the link, we can see an overview of the file on the right:
We can also choose "Dropbox" to do a separate search for Dropbox source, even though we are only a single source Dropbox:
We can click on the "Sources" icon and view all current information sources:
In the above, we can turn off this source, so the source is not being searched. You can also click "Details" to see all the information sources:
In the above we can see all the information about the Dropbox. If you are interested, we can click on the "Content" or "Source Settings" to check the contents of the source or modify the settings for this source.
Well, I talked about here today. In the next article, I'll describe how to create specific github source, and how to create a group and users. stay tuned!
reference:
【1】https://www.elastic.co/downloads/enterprise-search
【2】https://www.elastic.co/guide/en/workplace-search/current/workplace-search-dropbox-connector.html
