Configuring HTTP for the seedlist servlet | HCL Digital Experience
Learn how to configure HTTP for the seedlist servlet. The seedlist servlet requires HTTPs by default. Therefore, when you access the servlet through HTTP, WebSphere Application Server redirects you to HTTPs.
About this task
Procedure
- On the portal server, open the following file with an editor:
PortalServer_root/search/wp.search.servlets/seedlist/servletEAR/installableApps/wp.search.seedlist.ear/wp.search.servlets.seedlist.war/WEB-INF/web.xml
Cluster note: In a clustered environment, complete this step on the primary node and all secondary nodes. - Update the following code: Cluster note: In a clustered environment, complete this step on the primary node and all secondary nodes.
Replace it by the following code:<user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint>
<user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint>
- Save the file.Cluster note: In a clustered environment, complete this step on the primary node and all secondary nodes.
- Run the following portal ConfigEngine script: Cluster note: In a clustered environment, complete this step on the primary node only.
./ConfigEngine.sh action-update-ear-wp.search.servlets/seedlist/servletEAR
- Restart all servers in your configuration for your updates to take effect.
What to do next
- If your system is operating in a portal farm, continue on to Configuring search in a portal farm.
- If your system is operating in a clustered environment, continue on to Configuring search in a cluster.