WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Preparing for remote search service

This topic describes how you prepare the portal system for remote search service. You can provide remote search service by either using EJB or SOAP.

Notes for SOAP: If you use SOAP, the following security and performance considerations apply:

  1. Global security: If you use SOAP over a secure server, the SOAP service itself is not secure.

  2. Java 2 security: If you use SOAP, you need to disable Java 2 security.
You might consider disabling security before working with the remote search service for development or evaluation purposes. In this case disable global security on the IBM® WebSphere® Application Server server on which you install the remote search before you enable the remote search service for the portal. Proceed by the following steps:

  1. Access the administrative console.

  2. Click Security > Global security.

  3. Deselect Enable global security.

  4. This configuration takes effect after restarting IBM WebSphere Application Server. You will perform the required restart in a later step of the following procedure.

In order to enable the remote search service, perform the following steps on the machine where you want to install the remote service:

  1. Copy the files WebScannerSoap.ear, WebScannerEjbEar.ear, and PseLibs.zip to the was_profile_root/installableApps directory on the machine on which you want to install the remote search service. You find these files in the directory portal_server_root/installableApps of the portal installation.

  2. Depending on the requirements of your environment, install one of the two applications WebScannerEJbEar.ear or WebScannerSoap.ear on a server server1 . Proceed by the following steps:

    1. Access the administrative console.

    2. Select Applications > Install New Application.

    3. Browse and select WebScannerEjbEar.ear or WebScannerSoap.ear, depending on whether you are using EJB or Web service via SOAP.

    4. Click Next.

    5. On the following panels accept the default settings.

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

    7. Click Save to Master Configuration.

    8. Click Save.

  3. Optional: You only need to perform this step if you use Document Conversion Services.

    1. Install remote document conversion services on server1. For details about how to do this, refer to Enabling Document Conversion Services. You do not need to delegate all conversion tasks from the WebSphere Portal Express to server1. You only need to install the remote conversion services.

    2. Invoke the IBM WebSphere Application Server Administrative Console and select Environment > Shared Libraries. Create a new shared library named PSE with a classpath 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 IBM WebSphere Application Server cell name where DCS is installed.

    3. Click Apply > Save > Save to save your changes.

  4. Extract the Portal Search libraries and add them to the classpath on server1. To do this

    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 that you created in the previous step.

    3. Open the administrative console.

    4. Click Environment > Shared Libraries.

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

    6. Add the libraries extract/lib to the classpath by adding a new line to the classpath and giving the full path: was_profile_root/installableApps/extract/lib .

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

  5. Define a new Classloader for server1. To do this

    1. In the administrative console, click Servers > Application Servers, then click server1 .

    2. Under Server Infrastructure > Java and Process Management click Classloaders.

    3. Click New and then Apply.

    4. Under Additional Properties, click Libraries, then click Add.

    5. Select the Library Name PSE from the drop-down list and click OK.

    6. Save your changes to the configuration.

  6. On the administrative console, determine the required values for configuring the portlet parameters, depending on whether you are using EJB or Web service via SOAP:

    • For EJB: Determine the value for the port under Servers > 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 Server1 is configured to run. Determine the correct port number from Application servers > server1 > Ports > WC_defaulthost. The WC_defaulthost value is 10000; 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: 

      was_profile_root/installedApps/cell/WebScannerEar.ear/WebScannerSoap.war/
     wsdl/com/ibm/hrl/portlets/WsPSE/WebScannerLiteServerSOAPService.wsdl
      Replace the variables as follows:

      • was_profile_root is the profile directory of your WebSphere Application Server installation. For example, this can be: 

              /usr/WebSphere/AppServer(/profiles/profile_name)

      • cell is the cell name of your remote search machine.

      • WebScannerEar.ear is the name that you gave to the Enterprise Application when you installed 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 SOAP WC_defaulthost is 10000.

  7. In the administrative 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    Service Names:              Application Profiling Service, WorkArea, Security, Internationalization

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

  9. Start the application:

    1. Open the administrative console.

    2. Click Applications > Enterprise applications.

    3. Scroll to PSEStandalone or WebScannerEar. You can use the filter feature to search for these names.

    4. Click the checkbox and click Start. A message confirms that the application started successfully.

  10. Optional: This step is required only if you work with EJB on a secure server: Setting the search user ID.

  11. Optional: 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.

  12. Check that your remote search configuration works correctly.

  13. If required, re-enable security on the WebSphere Application Server.

  14. Back on the portal, configure Portal Search for remote search service. For details about how to do this refer to Configuring Portal Search for remote search service.

 

Parent topic:

Using remote search service