+

Search Tips   |   Advanced Search

Install remote search service using manual steps

We can install remote search service using manual steps instead of the IBM Install Manager.

  • For SOAP: For SOAP, the following security and performance considerations apply:

    1. Application security: For SOAP over a secure server, the SOAP service itself is not secure.

    2. Java 2 security: For SOAP, disable Java 2 security.

    SOAP support for remote search services was deprecated with HCL WebSphere Portal v8.0. EJB is still supported.

  • For EJB: For EJB, complete the following security administration tasks:

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

    2. Add the signer certification of the remote search service server into the portal search server. To do this addition...

      1. Access the WAS console of the portal search server.

      2. 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

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

      4. Click OK.

  1. Copy the files WebScannerSoap.ear, WebScannerEjbEar.ear, and PseLibs.zip to the directory APPSERVER_ROOT/installableApps on the computer on which to install the remote search service. We find these files in the following locations of the portal installation:

    • The files WebScannerSoap.ear and WebScannerEjbEar.ear are located in the directory PORTAL_HOME/prereq/prereq.webscanner/installableApps/WebScannerEjbEar.ear

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

  2. Depending on the requirements of the environment, install one of the two applications WebScannerEJbEar.ear or WebScannerSoap.ear on a remote server. For example, this can be server1.

    1. Access the WAS console.

    2. Click Applications > WebSphere Enterprise Application.

    3. Click Install.

    4. Browse and select WebScannerEjbEar.ear or WebScannerSoap.ear, depending on whether we are using EJB or web service through SOAP.

    5. Click Next.

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

    7. A message confirms the application PSEStandalone (for EJB) or the application WebScannerEar (for SOAP) was installed successfully.

    8. Click Save to Master Configuration.

    9. Click Save.

  3. Required: This step is required 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 HCL WebSphere Portal to the remote server. You only must install the remote conversion services. For more information, refer to the topic about Enable remote document conversion.

    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. Click Apply > Save > Save to save the changes.

  4. Extract the Portal Search libraries to the remote server and add them to the class path on the remote server. To do this step:

    1. Create a directory with the name extract under the directory installableApps.

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

    3. Open the WAS console.

    4. Click Environment > Shared Libraries.

    5. 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.

    6. 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

    7. Click Apply > Save to save the changes to the configuration.

  5. Add a reference from the application WebScannerEJbEar.ear to the shared library. To add a reference:

    1. Access the WAS console of the remote server and go to...

        Websphere enterprise applications

    2. For EJB, click...

        PSEStandalone | Shared library references

      For SOAP, click...

        WebScannerEar > Shared library references

    3. For EJB, on the window that opens up click the check box for PSEStandalone, then click the button Reference shared library.

      For SOAP: On the window that opens up click the check box for WebScannerEar, then click the button Reference shared library.

    4. From the Available list, select PSE.

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

    6. Click OK > OK.

    7. Save the configuration.

    8. For EJB: Restart the application PSEStandalone.

      For SOAP: Restart the application WebScannerEar.

  6. On the WAS console, determine the required values for configuring the portlet parameters, depending on whether we are using EJB or web service through SOAP:

    • For EJB: Determine the value for the port under Servers > Server Types > WebSphere application servers > YourAppServer1 > Communications > Ports > BOOTSTRAP_ADDRESS.

    • 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 Application servers > server1 > Ports > WC_defaulthost. The WC_defaulthost value is 10014; therefore, if you did not change the default, use this value. Make sure the port number set in the following file matches this port: 
      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 the WAS installation. For example, this directory can be:

          /usr/WebSphere/AppServer/profiles/profile_name

      • cell is the cell name of the remote search computer.

      • WebScannerEar.ear is the name that you gave to the Enterprise Application when installinged the WebScannerSoap.war file.

      Edit the file and look for the port given in the value for the SOAP address location. Example:

        <soap: address location="http://localhost:your_port_no/WebScannerSOAP/servlet/rpcrouter"/> .

      In the example the port is your_port_no. The default value for the WC_defaulthost is 10014.

  7. 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 (Ensure the Growable check box is selected.)     Service Names:              Application Profiling Service, WorkArea, Security, Internationalization

  8. Click Apply > Save to save the changes to the configuration.

  9. Start the application:

    1. Open the WAS console.

    2. Click Applications > Application Types > WebSphere enterprise applications.

    3. Scroll to PSEStandalone or WebScannerEar. Use the filter feature to search for these names.

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

  10. Required: This step is required only if we work with EJB on a secure server: Set the search user ID.

  11. 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 WAS.

  12. In the portal server enable CSIv2 identity assertion. To complete this step:

    In a clustered environment, complete these steps on the dmgr console.

    1. Enable CSIv2 Identity Assertion on the outbound connection:

      1. Access the WAS console of the portal server and go to...

          Security | Global Security | RMI/IIOP security | CSIv2 outbound communications | Use identity assertion

      2. When done, restart the portal server.

    2. Enable CSIv2 Identity Assertion on the inbound connection:

      1. Access the WAS console of the remote server and select...

          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.
      For more detailed information, refer to the WAS information center.

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

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


Parent Remote search service