Prepare for remote search service

1. Prepare security for remote search service in a single-signon domain (SSO).

2. Add the signer certificate of the search service server into the portal server...

   1. Access the WAS console of the portal server and click...
      Security | SSL certificate and key management | Key stores and certificates | NodeDefaultTrustStore | Signer certificates | Retrieve from port

      In a clustered environment, the path is...

      Security | SSL certificate and key management | Key stores and certificates | CellDefaultTrustStore | Signer certificates | Retrieve from port

   2. Enter the remote search service server host, its SOAP port, and an alias.

   3. Click OK.

3. On the computer on which to install the remote search service, copy WebScannerEjbEar.ear and PseLibs.zip to...
   APPSERVER_ROOT/installableApps

   You find these files in the following locations...

   • WebScannerEjbEar.ear is located in the directory...
     PORTAL_HOME/search/prereq.webscanner/installableApps

   • The file PseLibs.zip is located under directory...
     PORTAL_HOME/search/wp.search.libs/installableApps

4. Install WebScannerEJbEar.ear on a remote server. For example, this can be server1...

   1. Access the WAS console and click...
      Applications | WebSphere Enterprise Application | Install | WebScannerEjbEar.ear | Next

   2. On the following panels, accept the default settings.

   3. A message confirms the application PSEStandalone was installed successfully.

   4. Click Save to Master Configuration.

   5. Click Save.

5. If we use Document Conversion Services...

   1. Install remote document conversion services on the remote server.

      We do not need to delegate all conversion tasks from the WebSphere Portal to the remote server. You only must install the remote conversion services.

   2. Invoke the WAS console and select...
      Environment | Shared Libraries

      Create a new shared library named PSE with a class path as follows:

      $(APP_INSTALL_ROOT)/cell/dcs_war.ear/dcs.war/WEB-INF/lib/convertors.jar
      $(APP_INSTALL_ROOT)/cell/dcs_war.ear/dcs.war/WEB-INF/lib/Export.jar

      ...where cell is the WAS cell name where DCS is installed.

   3. Save changes...
      Apply | Save | Save

6. Extract the Portal Search libraries to the remote server, and add them to the class path on the remote server...

   1. Create directory...
      installableApps/extract

   2. Locate PseLibs.zip in installableApps and extract its content into the directory extract created in the previous step.

   3. Open the WAS console and click....
      Environment | Shared Libraries

   4. Create or modify the new shared library names PSE.

      When creating the library, check the option...

      Use an isolated class loader for this shared library

   5. Add the libraries extract/lib to the class path by adding a new line to the class path and giving the full path:
      APPSERVER_ROOT/installableApps/extract/lib

      APPSERVER_ROOT is the profile directory of the WAS installation. For example, this path can be:

      /usr/WebSphere/AppServer/profiles/profile_name

   6. Save changes to the configuration...
      Apply | Save

7. Add a reference from the application WebScannerEJbEar.ear to the shared library...

   1. Access the WAS console of the remote server and navigate to...
      Websphere enterprise applications | PSEStandalone | Shared library references

   2. On the window that opens up click the check box for PSEStandalone, then click the button...
      Reference shared library

   3. From the Available list, select PSE.

   4. Click the appropriate arrow so that PSE displays in the Selected list.

   5. Click OK | OK.

   6. Save the configuration.

   7. Restart the application PSEStandalone.

8. On the WAS console, determine the required values for configuring the portlet parameters...
   Servers | Server Types | WebSphere application servers | YourAppServer1 | Communications | Ports | BOOTSTRAP_ADDRESS

9. In the WAS console, under...
   Resources | Asynchronous beans | Work managers

   ...create a new Work manager named PSEWorkManager with the following attributes:

          
      Name:         PSEWorkManager
      JNDI Name:    wps/searchIndexWM
      Minimum Number of Threads:  20
      Maximum number of Threads:  60
      Growable =    True (Verify the Growable check box is selected.)     
      Service Names: Application Profiling Service, WorkArea, Security, Internationalization
   

10. To save the changes to the configuration...
    Apply | Save

11. Start the application:

    1. Open the WAS console and click...
       Applications | Application Types | WebSphere enterprise applications

    2. Scroll to PSEStandalone or WebScannerEar.

    3. Click the check box and click Start. A message confirms the application started successfully.

12. If we work with EJB on a secure server: Set the search user ID.

13. If you disabled security or set the search user ID by one of the optional previous steps: Restart the WAS.

14. In the portal server enable CSIv2 identity assertion. In a clustered environment, complete these steps on the dmgr WAS console.

    1. Enable CSIv2 Identity Assertion on the outbound connection:

       1. Access the WAS console of the portal server and check...
          Security | Global Security | RMI/IIOP security | CSIv2 outbound communications | Use identity assertion

       2. When we are done, restart the portal server.

    2. Enable CSIv2 Identity Assertion on the inbound connection:

       1. Access the WAS console of the remote server and check...
          Security | Global Security | RMI/IIOP security | CSIv2 inbound communications | Use identity assertion

       2. Under Trusted identities, enter either an asterisk (*) or the identity of the portal server.

       3. When we are done, restart the remote server.

15. 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 us to HTTPs

    1. Edit:
       PortalServer_root/search/wp.search.servlets/seedlist/servletEAR/installableApps/wp.search.seedlist.ear/wp.search.servlets.seedlist.war/WEB-INF/web.xml

       In a clustered environment, complete this step on the primary node and all secondary nodes.

    2. Update the following code:

       In a clustered environment, complete this step on the primary node and all secondary nodes.

       <user-data-constraint>          <transport-guarantee>CONFIDENTIAL</transport-guarantee>
       </user-data-constraint>
       

       Replace it by the following code:

       <user-data-constraint>          <transport-guarantee>NONE</transport-guarantee>
       </user-data-constraint>
       

    3. Save the file.

       In a clustered environment, complete this step on the primary node and all secondary nodes.

    4. Run the following portal ConfigEngine script:

       In a clustered environment, complete this step on the primary node only.

       ./ConfigEngine.sh action-update-ear-wp.search.servlets/seedlist/servletEAR

    5. Restart all servers in the configuration for the updates to take effect.

16. Back on the portal, configure Portal Search for remote search service.

    In a clustered environment, complete this step on the primary node only.

Related tasks:
Configure a remote Document Conversion Service
Set the search user ID
Configure a remote search service