SIEMENS Active Workspace 3.4 Indexing and Search Deployment and Configuration AW030 • 3.4 Contents Indexing . 1-1 Indexing deployment strategy . 1-1 Indexer component . 1-1 Hardware considerations for TcFTSIndexer . 1-2 Indexing deployment mode . 1-2 Optimize hardware for indexing . 1-3 Determine indexing strategy . 1-6 Install indexing . 1-8 Installing indexing components . 1-8 Installing Indexing Engine . 1-10 Installing the Indexer . 1-18 Patch indexing components . 1-25 Configure object data indexing . 1-27 Prepare to configure indexing . 1-27 Configure indexing . 1-29 Troubleshoot indexing . 1-38 Find logs related to indexing . 1-38 Troubleshoot indexing object data . 1-41 Troubleshoot TcFTSIndexer . 1-43 Troubleshoot indexing performance . 1-44 Troubleshoot Solr issues . 1-45 Using indexing utilities . 1-47 Indexing utilities . 1-47 Customize indexing . 1-55 Overview of indexer customization . 1-55 Indexer customization prerequisites . 1-55 TcFTSIndexer installation layout . 1-55 TcFTSIndexer extensibility framework . 1-56 Object data indexing steps . 1-57 Run a sample search indexing flow . 1-59 Adding search indexing steps . 1-61 Adding new search indexing types . 1-63 Deploy a new search indexing type . 1-63 Modify an existing search indexing type . 1-64 Adding search indexing flows . 1-64 ObjData indexing support for saved queries . 1-65 Indexing non-Teamcenter data . 1-65 Search . 2-1 Configure search . 2-1 Search configuration tasks . 2-1 Define index data and filters . 2-1 AW030 3.4 Indexing and Search Deployment and Configuration 3 CoContentsntents Configure search suggestions . 2-5 Define search prefilters . 2-6 Preserve global search Select:Type prefilter . 2-8 Prioritizing facet categories in the filter panel . 2-8 Setting the default search operator . 2-9 Adding wildcards to searches automatically . 2-10 Allow searching for common words . 2-10 Add synonyms to searches . 2-11 Defining the high-priority properties to display in search results . 2-11 Return the parent business object for a dataset . 2-11 Configuring search prefilters for object sets . 2-12 Enabling Advanced Search . 2-14 Setting revision rules for searching . 2-15 Indexing and searching alternate IDs in Active Workspace . 2-16 Filtering object data with a custom user exit method . 2-17 Example search results . 2-19 Troubleshooting search . 2-19 Find logs related to search . 2-19 Troubleshoot search results . 2-20 Troubleshoot search performance . 2-21 Customize Solr . 2-22 Configure Solr for HTTPS communication . 2-22 SolrCloud overview . 2-23 Solr URL single point-of-failure . 2-23 Enable SolrCloud authentication . 2-24 4 Indexing and Search Deployment and Configuration AW030 3.4 Chapter 1: Indexing Indexing deployment strategy Indexer component The TcFTSIndexer is a four-tier SOA client that exports Teamcenter data for importing into the Solr database. The TcFTSIndexer orchestrator is the main component for indexing and is comprised of steps that run in sequential order. The steps are Query, Export, Transform, and Load. 1. The TcFTSIndexer orchestrator connects to Teamcenter and does the initial validation. It reads the configuration for start and end time, and then breaks down the time into configurable time slices for query. 2. The TcFTSIndexer orchestrator creates a new thread that connects to Teamcenter and gets the list of UIDs. 3. The TcFTSIndexer orchestrator reads the output UID file and chunks the data into a manageable size, and then calls TIE export by connecting to the pool manager. This step creates the Teamcenter XML file. 4. The TcFTSIndexer orchestrator converts the Teamcenter XML file to a Solr input XML file with the security read expressions. 5. The TcFTSIndexer orchestrator loads the Solr input XML file into Solr. 6. The TcFTSIndexer orchestrator connects to the pool manager and calls to confirm export. AW030 3.4 Indexing and Search Deployment and Configuration 1-1 ChCaphtaeprte1r: 1:IndexInindgexing Hardware considerations for TcFTSIndexer When planning your indexing deployment strategy, consider the hardware where you want to install the indexing components. The number of machines and the resources available on the machines help determine how you should configure the TcFTSIndexer environment. Some of the hardware considerations for TcFTSIndexer are based on memory, storage type, and CPU usage by the TcFTSIndexer components: • TcFTSIndexer orchestrator Runs a Java process that runs the query, TIE export, transform, and load operations in stand-alone mode. At high levels of parallelization, transform is more CPU and memory intensive. • Pool manager For object data indexing, the TcFTSIndexer orchestrator connects to the pool manager to run the query, TIE export, and load operations. These operations run on multiple tcserver instances and connect to the database for SQL calls. • Solr Solr is CPU-intensive during query calls and can be memory intensive during large dataset file indexing, as well as I/O intensive for reading and writing many documents. • Teamcenter database The database is intensive in all areas of hardware use due to the number of requests that it handles in a short time. These requests can be CPU-intensive, and the SQL calls require both reading and writing to tables, which is I/O and memory intensive. Careful consideration of the database configuration and hardware requirements should be a priority. To achieve optimal performance, Siemens PLM Software strongly recommends that these components are installed on separate machines designed for their particular use, Indexing performance also relies on the number of parallel threads that can be simultaneously completed. The number of threads is controlled by the tc.maxConnections property, but it must be coordinated with the number of warmed up servers in the pool manager and the number of threads that the.