2c8 Server Search
Overview
Installation
Requirements
Performing the installation
Configuring 2c8 Server Search
Files
Schedule
Directories
Indexer
SharePoint
Implementation details
Centuri
Configuring 2c8 Modeling Tool
Installation and setup
2c8 Server Search
2c8 Server Search
2c8 Server Search
Table of Content
1 OVERVIEW
2 INSTALLATION
2.1 REQUIREMENTS
2.2 PERFORMING THE INSTALLATION
3 CONFIGURING 2C8 SERVER SEARCH
3.1 FILES
3.1.1 Schedule
3.1.2 Directories
3.1.3 Indexer
3.2 SHAREPOINT
3.2.1 Implementation details
3.3 CENTURI
4 CONFIGURING 2C8 MODELING TOOL
Overview
Chapter 1
Overview
2c8 Server Search is a component for delivering better search results to published material from 2c8 Modeling Tool. 2c8 Server Search can search in file structures, SharePoint and Centuri. When searching in a file structure a file index is used and when using SharePoint or Centuri the search query is passed on to the respective service.
Installation
Chapter 2
Installation
2.1 Requirements
The search component requires the GlassFish application server installed with the 2c8 Server Component. Running the search component without the 2c8 server component is not possible.
2.2 Performing the installation
Login to the GlassFish admin console (http://localhost:4848/common/index.jsf) and click on the "Applications" node in the tree. Click the "Choose File" button and select the mt-search-1.0.war file. Then change the "Context Root" to "mt-search" and click the "OK" button.
Figure 2. 1
Deploying the search component.
Configuring 2c8 Server Search
Chapter 3
Configuring 2c8 Server Search
Go to http://localhost:8080/mt-search/ and login with a 2c8 Modeling Tool user that has administrator privileges (the default user is "admin" with password "2c8").
3.1 Files
The file indexer walks through a directory tree and scans any document it finds. It will read any Microsoft Office, PDF, HTML or text document it finds and add it to the search index. Published models from 2c8 Modeling Tool will also be indexed if found.
3.1.1 Schedule
The file indexer can be scheduled to update the search index periodically. New files will be added, updated files will be rescanned and removed documents will be removed from the search index.
3.1.2 Directories
To add directory roots to file indexer enter a path and optionally a root and click "Add Directory...". The root can be empty, but if it is specified then files found in the path will be rewritten to start with the root. This might be used if the files are available to to the server that runs the search indexer but not to clients. To reach the files the clients have to go through a web server. For example, if we add the path "g:\documents" with the root "http://www.ex.com/files", a document found in "g:\documents\strategy\start.docx" will be rewritten to "http://www.ex.com/files/strategy/start.doc".
3.1.3 Indexer
The file indexer can be started and stopped manually if necessary. Information about the index is displayed below the buttons.

Status
Shows the current status of the file indexer.

Files in index
Shows the number of files in the index.

Last scan completed
Shows the last time and date when the file indexer completed a scan.

Next scan
Shows when the next scan will start, if it is enabled.

Index path
Shows the path to the search index. To clean the index remove the files in this directory.

3.2 SharePoint
If this option is enabled searches from a client will be passed to a SharePoint server via SharePoint's REST API. For authentication to work SharePoint must be configured to handle NTLM.

Host
The address of the SharePoint server.

Port
The port number of the Sharepoint server.

Domain
The SharePoint domain. If more than one domain is running on the same server the request needs to specify which domain to query. If this is left empty the host is used as domain, which in most cases will be correct.

Username
Username that is used to call the SharePoint search API.

Password
Password user that is used to call the SharePoint search API.

3.2.1 Implementation details
When a client requests a search the search component opens a connection to http://${host}:${port}/_api/search/query?querytext='<search string>' using NTLM authentication.
3.3 Centuri
If this option is enabled searches from a client will be passed to a Centuri server via Centuri's SOAP API.
The required settings are the same as the Centuri plugin for 2c8 Modeling Tool. To see the settings in 2c8 Modeling Tool select Tools/Settings... from the menu and then click "Plug-in". Select the plugin "Centuri Documents" under the "Installed" tab and click on the "Settings..." button. Copy the settings from this dialog.
Figure 3. 1
Settings can be copied from 2c8 Modeling Tool.

Server address
The address to the Centuri server.

Database name
The name of the database to search in.

Web service address
The address to the Centuri web server

Use trusted connection
If select no username or password is needed.

Username
Username that is used to call the Centuri search API.

Password
Password that is used to call the Centuri search API.

Configuring 2c8 Modeling Tool
Chapter 4
Configuring 2c8 Modeling Tool
To make published material use 2c8 Server Search, the publish profile needs to be configured with the correct address. Start 2c8 Modeling Tool and open a repository. Select "Tools/Publish..." from the menu and edit a web profile. Select "Layout" and then the "Functions" tab. Check the box "Use external search engine" and enter the address to the GlassFish server. Eg. if the hostname of the GlassFish server is "localhost" and the port is 8080 then enter "http://localhost:8080" in the URL field.
Figure 4. 1
Configuring 2c8 Modeling Tool - Web Profile