Preparing for remote search service | HCL Digital Experience
Get an overview of how you prepare your portal system for remote search service. You can provide remote search service by either using EJB or SOAP.
Before you begin
- For SOAP: If you use SOAP, the following security and performance
considerations apply:
- Application security: If you use SOAP over a secure server, the SOAP service itself is not secure.
- Java 2 security: If you use SOAP, you must disable Java 2 security.
Note: SOAP support for remote search services was deprecated with HCL DX Portal Version 8.0. EJB is still supported. - For EJB: If you use EJB, complete the following security administration
tasks:
- Prepare security for remote search service in a single-signon domain (SSO).
- Add the signer certification of the remote search service server
into the portal search server. To do this addition, proceed by the
following steps:
- Access the WebSphere® Integrated Solutions Console of the portal search server.
- Click Cluster note: In a clustered environment, the path is .
.
- Enter the remote search service server host, its SOAP port, and an alias.
- Click OK.
Procedure
- Copy the files WebScannerSoap.ear, WebScannerEjbEar.ear, and PseLibs.zip to the directory
AppServer_root/installableApps
on the computer on which you want to install the remote search service.You find these files in the following locations of your portal installation:- The files WebScannerSoap.ear and
WebScannerEjbEar.ear are in the directory
PortalServer_root/search/prereq.webscanner/installableApps
- The file PseLibs.zip is located under
directory
PortalServer_root/search/wp.search.libs/installableApps
- The files WebScannerSoap.ear and
WebScannerEjbEar.ear are in the directory
- Depending on the requirements of your environment, install
one of the two applications WebScannerEJbEar.ear or WebScannerSoap.ear on a remote
server. For example, this can be server1. Proceed by the following steps:
- Access the WebSphere® Integrated Solutions Console.
- Click .
- Click Install.
- Browse and select WebScannerEjbEar.ear or WebScannerSoap.ear, depending on whether you are using EJB or web service through SOAP.
- Click Next.
- On the following panels, accept the default settings.
- A message confirms that the application PSEStandalone (for EJB) or the application WebScannerEar (for SOAP) was installed successfully.
- Click Save to Master Configuration.
- Click Save.
- Required: This step is required if you use
Document Conversion Services.
- Extract the Portal Search libraries to the remote server
and add them to the class path on the remote server. To do this step,
proceed as follows:
- Add a reference from the application WebScannerEJbEar.ear to the shared library. To add a reference, proceed as follows:
- Access the WebSphere® Integrated Solutions Console of the remote server.
- Navigate to Websphere enterprise applications.
- For EJB: Click the application . For SOAP: Click the application .
- For EJB: On the window that opens up click the check box for PSEStandalone, then click Reference shared library. For SOAP: On the window that opens up click the check box for WebScannerEar, then click Reference shared library.
- From the Available list, select PSE.
- Click the appropriate arrow so that PSE displays in the Selected list.
- Click .
- Save the configuration.
- For EJB: Restart the application PSEStandalone. For SOAP: Restart the application WebScannerEar.
- On the WebSphere® Integrated Solutions Console, determine the required values for configuring the portlet
parameters, depending on whether you are using EJB or web service
through SOAP:
- For EJB: Determine the value for the port under .
- For SOAP: Determine the value for the
port number for the SOAP URL parameter. The appropriate port number
for the SOAP URL parameter is the port on which the application server
runs, in other words, the HTTP transport on which the remote server
is configured to run. Determine the correct port number from
AppServer_root/installedApps/cell/WebScannerEar.ear/WebScannerSoap.war/ wsdl/com/ibm/hrl/portlets/WsPSE/WebScannerLiteServerSOAPService.wsdl
Replace the variables as follows:AppServer_root
is the profile directory of your WebSphere® Application Server installation. For example, this directory can be:
For z/OS® this directory can be:/usr/WebSphere/AppServer/profiles/profile_name
/WebSphere/VR1M0/AppServer/profiles/default
-
cell
is the cell name of your remote search computer. -
WebScannerEar.ear
is the name that you gave to the Enterprise Application when you installed theWebScannerSoap.war
file.
In the example the port is<soap: address location="http://localhost:your_port_no/WebScannerSOAP/servlet/rpcrouter"/> .
your_port_no
. The default value for the WC_defaulthost is 10014.
. The WC_defaulthost value
is 10014; therefore, if you did not change the default, you can use
this value. Make sure that the port number that is set in the following
file matches this port:
-
In the WebSphere® Integrated Solutions Console, go to , create a new Work manager who is named PSEWorkManager with
the following attributes:
WebSphere Application Server V9: If you upgraded to IBM® WebSphere® Application Server Version 9.0, the WebSphere® Integrated Solutions Console path is .
Name: PSEWorkManager JNDI Name: wps/searchIndexWM Minimum Number of Threads: 20 Maximum number of Threads: 60 Growable = True (Ensure that the Growable check box is selected.) Service Names: Application Profiling Service, WorkArea, Security, Internationalization
- Click to save your changes to the configuration.
- Start the application:
- Required: This step is required only if you work with EJB on a secure server: Setting the search user ID.
- Required: This step is required only if you disabled security or set the search user ID by one of the optional previous steps: Restart the WebSphere® Application Server.
- In the portal server enable CSIv2 identity assertion. To
complete this step, proceed as follows:Cluster note: In a clustered environment, complete these steps on the Deployment Manager WebSphere® Integrated Solutions Console.
- On the portal server, configure HTTPs for the Seedlist
servlet. The Seedlist servlet requires HTTPs by default. Therefore, when you access the servlet through HTTP, then WebSphere® Application Server redirects you to HTTPs. Proceed by the following steps:
- Back on your portal, configure Portal Search for remote
search service. Cluster note: In a clustered environment, complete this step on the primary node only.