Web Search Integration

Prerequisite

Before you can start with this chapter, you need to have finished the following parts:

Setup Product 360 Permissions for Web Search

There are 2 different kinds of Product 360 Core Users for different Product 360 - Web Search use cases:

  1. Product 360 - Web User

    • This user runs search queries from within the User Interface of Product 360 Web.

  2. Product 360 - Desktop User

    • This administrator user manages the search indices from within Product 360 Desktop. He can manually create indices, trigger or schedule the incremental index updates.

Permission Settings for Product 360 - Web User to use Web Search

The Product 360 - Web User need the following interface visibility rights at least:

No.

Rights

Type

Category

Permission

1

Interface Visibility

Informatica Product 360 view

Search Index

Search Index

It is recommended to set all necessary Product 360 - Web permission as described in: Product 360 - Web Configuration.

Permission Settings for Product 360 - Desktop User to use Web Search Index Build

The Product 360 - Desktop User needs the following action rights:

No.

Rights group

Permission

1

Export

Export Format Template, general access

2

Export

Export Profile, general access

Please ensure to have all permission to entities, fields and attributes that are defined in the index configuration.

Setup Configuration for Product 360 - Repository

The entities, sub-entities and their fields which are defined for Web Search should be enabled for export on Product 360 - Repository in the file Repository.repository, located in <PIM_SERVER_INSTALLATION_ROOT>\server\configuration\HPM.

The Product 360 Server has to be restarted in order to have changes take effect.

Setup Configuration for Product 360 - Core

The configuration properties for Web Search on Product 360 Core can be defined in the property file server.properties, located in <PIM_SERVER_INSTALLATION_ROOT>\server\configuration\HPM.

The Product 360 Server has to be restarted in order to have changes take effect.

No.

Property

Default Value

Description

Remarks

1

system.name

Specifies the name of the system

Specifies the name of the system, e.g. Test System /Productive System / Demo / Poad etc.
The system name will also be used as a prefix for fulltextsearch index name.
Blanks will be replaced with _. Best practice: use 0-9A-Za-z.-

2

fulltextsearch.enabled

true

Enable/disable full-text search

Full-text search can be enabled (default) or disabled.
If full-text search is enabled, ensure you setup the Elasticsearch integration properties.

3

fulltextsearch.rest.url

http://localhost:9200

URL path to the Elasticsearch REST server.

Depending where the Elasticsearch server is located, the server name (e.g. localhost) and port (e.g. 9200) can be different.

Incase a multi-server Elasticsearch cluster is created, a comma separated list of the server name and port should be provided.
E.g. elasticsearch.rest.url = http://localhost:9200,http://localhost:9201

4

fulltextsearch.rest.user

Login name of the Elasticsearch REST server.

If not using user and password combination, please leave this field empty, but active

5

fulltextsearch.rest.password

Login password of the Elasticsearch REST server.

If not using user and password combination, please leave this field empty, but active

6

fulltextsearch.rest.allow.self-signed.certificate

true

Allows self-signed certificate only if you use https.

Setup Configuration for Product 360 - Desktop

The search index can only be created, if the fulltextsearch.enabled=true in server.properties.

In order to create a search index,

  1. An export format template needs to be defined with -

    • Purpose - Full-text search

    • Post-processing export step - Search index synchronization

    • File management -

      • Extended options - true

      • Output files -

      • config-file

        • Format - JSON

        • Encoding - UTF-8

      • data-file

        • Format - JSON

        • Encoding - UTF-8

  2. An Full-text search profile needs to be defined using the above export format template and executed.

  3. This Full-text search profile will create a search index in the Elasticsearch server.

  4. The above Full-text search profile should be scheduled to run for incremental indexing.

Setup Configuration for Product 360 - Web

The configuration properties for Web Search on Product 360 Web can be defined in the property file webfrontend.properties, located in <PIM_SERVER_INSTALLATION_ROOT>\server\configuration\HPM.

No.

Property

Default Value

Description

1

 
web.client.hps.max.display.facet

5

Maximum number of displayed search facets.