Knowledge articles are not displayed in Service Point
search cancel

Knowledge articles are not displayed in Service Point

book

Article ID: 382521

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager CA Service Catalog CA Service Desk Manager

Issue/Introduction

The suggested Solutions section does not display any Knowledge Article from Service Desk Manager.

The browser console shows a 400 HTTP Error. 

Search server is up and running. Indexes are created and populated.

Environment

Service Management 17.4

xFlow 17.4

Search Server 17.4

Cause

The search microservice is not running due to a port conflict issue when starting the search microservice.

Resolution

Each xFlow microservice needs to use a different port number.

When creating the .txt file in step  4 to enable SSL for xFlow a different and available port number must be configured for each microservice.

Example:

echo -Dhttps.port=9444 -Dplay.server.https.keyStore.path=C:\certificates\hostname_keystore.jks -Dplay.server.https.keyStore.password=(keystore password) > incidentmicroservice-17.0.479\INCIDENTMICROSERVICE_config.txt

echo -Dhttps.port=9446 -Dplay.server.https.keyStore.path=C:\certificates\hostname_keystore.jks -Dplay.server.https.keyStore.password=(keystore password) > collabmicroservice-17.0.479\COLLABMICROSERVICE_config.txt

echo -Dhttps.port=9448 -Dplay.server.https.keyStore.path=C:\certificates\hostname_keystore.jks -Dplay.server.https.keyStore.password=(keystore password) > insightmicroservice-17.1.706\INSIGHTMICROSERVICE_config.txt

echo -Dhttps.port=9450 -Dplay.server.https.keyStore.path=C:\certificates\hostname_keystore.jks -Dplay.server.https.keyStore.password=(keystore password) > pushmicroservice-17.0.479\PUSHMICROSERVICE_config.txt

echo -Dhttps.port=9452 -Dplay.server.https.keyStore.path=C:\certificates\hostname_keystore.jks -Dplay.server.https.keyStore.password=(keystore password) > searchmicroservice-17.0.479\SEARCHMICROSERVICE_config.txt      

In the example above, the Search microservice is using port 9452 and each microservice has a different port number.