Installation Scenario - Indexing and Search Service

Skip to end of metadata
Go to start of metadata

Installation Scenario - Indexing and Search Service for Oracle Communications Unified Communications Suite
Version 1 Update 3

Topics:

Overview of This Scenario

The following installation information describes how to install and configure Indexing and Search Service for Oracle Communications Unified Communications Suite. Before proceeding, make sure that you have already made your architectural and design decisions. For example, you should already know the total number of servers in your deployment, the number of front-end and back-end servers, and similar details. If you are still in the planning or evaluating process, see the following documents:

Some of this information assumes that you are using Solaris Operating System (Solaris OS) 10. For Red Hat Linux, substitute the respective Red Hat Linux commands.

Assumptions

This scenario shows how to install Indexing and Search Service on a separate host.

Which Software Components and Downloads Do You Need?

  • Communications Suite: Messaging Server, Indexing and Search Service, and GlassFish Message Queue, bundled together as part of the Oracle Communications Unified Communications Suite download
  • Communications Suite patches, created after the initial release of Communications Suite 7 Update 2
  • Application server web container for Indexing and Search Service: Sun GlassFish Enterprise Server
  • LDAP server: Directory Server
  • (Optional): Apache HTTP Server version 2, for multi-host deployments (used as web container for ISS back ends)

Download sites: Get the Software

Installing and Configuring an Indexing and Search Service Deployment

Installing ISS involves the following high-level steps:

1. Before You Install and Configure ISS

Complete the following prerequisites for installing and configuring ISS:

  1. Review Requirements for Communications Suite 7 Update 2 for the operating system, patch, client software, and disk space needed, and any additional software requirements for this release of Indexing and Search Service.
  2. Install and configure the following required software:
  3. Make sure that the Messaging Server host for your ISS deployment is running Messaging Server 7 Update 4 and GlassFish Message Queue 4.4 Update 1.
  4. On Messaging Server and ISS hosts, define and set up additional product requirements. Make sure that the Network Time Protocol (NTP) service is running on both the Messaging Server and the ISS hosts.
    • Solaris OS:
      # svcadm enable ntp
      # svcs ntp
      STATE          STIME    FMRI
      online         16:35:43 svc:/network/ntp:default
      

      See the section about time-related services in System Administration Guide: Network Services for more information about NTP on Solaris.

    • Red Hat Linux:
      # cd /etc/rc3.d
      # ln -s ../init.d/ntpd S74ntpd
      # ../init.d/ntpd start
      Starting ntpd:                                             [  OK  ]
      # ps -ef | grep ntp
      ntp       2347     1  0 20:56 ?        00:00:00 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
      

      See the section about NTP in Red Hat Documentation for more information about NTP on Red Hat Linux.

2. Install, But Do Not Configure, ISS Software

  1. To install the ISS software, run the Communications Suite installer, for example:
    ./commpkg install
    
  2. Select option 6: Indexing Search Services 1u1.
  3. For information about running the Communications Suite installer, see Installing Communications Suite.
  4. For multi-host deployments, run the Communications Suite installer on each host in your multi-host deployment to install the ISS software.
    Note
    Deploying ISS involves installing then configuring the software. In this section, you only install the software. You configure the ISS software in a later step.
  5. Install current ISS patch.
    See Indexing and Search Service Patches by Release for latest patch information.
    Note
    You currently "patch up" to Indexing and Search Service 1 Update 4.

3. Gather Information Required to Configure ISS

Complete the Configuration Worksheet to prepare for Messaging Server for Indexing and Search Service integration and to configure Indexing and Search Service.

4. Prepare Messaging Server for ISS

See Preparing Messaging Server for Indexing and Search Service Integration.

5. Decide on ISS Installable Components

You can install all the ISS components onto a single host or spread the installation across multiple hosts. The four ISS components include:

  • web
  • jmq
  • ldap
  • index
Web (web)

This component contains the front-end web server access to the index services. This component must be GlassFish Server and must support the asadmin command. The setup script installs and configures the following three JAR files on the GlassFish Server:

  • rest. This component is the RESTful API. You access the RESTful service at the following URL:
    http://<host>:<port>/rest
    
  • searchui. This component is a sample search UI. You access the sample search UI at the following URL:
    http://<host>:<port>/searchui
    
  • storeui. This component controls access to the attachment store. You access it at the following URL:
    http://<host>:<port>/storeui
    
Oracle GlassFish Message Queue (jmq)

This component is Oracle GlassFish Message Queue for the Indexing and Search Services. The GlassFish Server and index services use this message bus to communicate.

Directory Service (ldap)

ISS requires Directory Server for Java Naming and Directory Interface (JNDI) lookups.

Indexing (index)

This component contains the following core index and search services that are required for normal operation:

  • Index Service (indexSvc) – Bootstraps new users and indexes incoming content.
  • Search Service (searchSvc) – Searches index and returns results.
  • JMQ Consumer (jmqconsumer) – Listens to the JMQ on the message store and notifies indexSvc if new content requires indexing.
  • Util Service (utilSvc) – Provides utility services to Index Service.
  • Apache (httpd) – Used only in multimachine deployments, provides access to the attachment store.

6. Configure GlassFish Message Queue 4.4u1 on the ISS Host

    1. Ensure that the GlassFish Message Queue broker is running and is enabled to start at reboot. Edit the imqbrokerd.conf file (/etc/imq/imqbrokerd.conf on Solaris OS and /etc/opt/sun/mq/imqbrokerd.conf on Red Hat Linux) to contain the following information. Check the file permissions and change them to be writeable if they are set to read-only.
      AUTOSTART=YES
      ARGS=-vmargs -Xmx1024m
      RESTART=YES
      
    2. If the config.properties file (/var/imq/instances/imqbroker/props/config.properties on Solaris OS and /var/opt/sun/mq/instances/imqbroker/props/config.properties on Red Hat Linux) does not yet exist, start the IMQ broker for the first time to generate it.
      nohup /etc/init.d/imq start
      
    3. Tune the GlassFish Message Queue broker properties by editing the bottom of the config.properties file (/var/imq/instances/imqbroker/props/config.properties on Solaris OS and /var/opt/sun/mq/instances/imqbroker/props/config.properties on Red Hat Linux) to contain the following information.
      You might need to check the file permissions and change them to be writeable if set to read-only. The defaults for these settings appear in the default.properties file (/usr/share/lib/imq/props/broker/default.properties on Solaris OS and /opt/sun/mq/private/share/lib/props/broker/default.properties on Red Hat Linux).
      imq.portmapper.backlog=-1
      imq.autocreate.destination.limitBehavior=REMOVE_OLDEST
      imq.autocreate.destination.maxNumProducers=-1
      imq.autocreate.reaptime=7200
      imq.destination.DMQ.truncateBody=true
      imq.jms.max_threads=2000
      
    4. Ensure that the Message Queue broker is restarted to acquire the new settings:
      /etc/init.d/imq stop
      nohup /etc/init.d/imq start
      

7. Complete the ISS Installation

Use the tasks in this section to complete the ISS installation on either a single host or multiple hosts.

To Configure Indexing and Search Service on a Single Host
  1. Change to the jiss/bin directory, for example:
    cd /opt/sun/comms/jiss/bin
    
  2. Run the initial configuration.
    ./setup
    
  3. Answer the series of configuration prompts.
    For more information, see Indexing and Search Service Initial Configuration.
  4. Restart GlassFish Server.
    cd /opt/SUNWappserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    
  5. Run Post Configuration Procedures.
    See Indexing and Search Service Post Configuration.
To Configure Indexing and Search Service on Multiple Hosts

For multi-host deployments, see Using setup in a Multi-host Environment.

8. Index (Bootstrap) Users

Use the issadmin.sh --bootstrap command to index users.

For example, to index a single user:

# ./issadmin.sh --bootstrap --user <username> --host <hostname> --runoptimizer true

To index a list of users, 16 users at time:

# ./issadmin.sh --bootstrap --accountlist /tmp/accountlist.txt --threads 16 --runoptimizer true --altoutput /tmp/parallelbootstrap.log

9. Verify the ISS Installation

  1. You can search a user's content by accessing it in a browser at the following URL:
    http://<host>:<port>/rest
    

    Log in as the user or proxy auth as the read-only store admin user (mail.imap.admin.username, mail.imap.admin.username).

  2. To view a demo web application utilizing the ISS API, try the SearchUI link or access the following URL in a browser:
    http://<host>:<port>/searchui
    

    Try a search such as +body:java to search for attachments from email with the word "java" in the body.

  3. Finally, send a new email message to an indexed user and confirm that the new message appears in the search.

10. (Optional) Configure Messaging Server to Use ISS for IMAP SEARCH

  1. Set service.imap.indexer.enable to 1, which redirects IMAP SEARCH queries to ISS for fulfillment:
    cd <msg-svr-base>/bin
    ./configutil -o service.imap.indexer.enable -v 1
    
  2. This parameter is refreshable, so a refresh of the configuration is sufficient to enable the change.
    ./refresh imap
    

11. (Optional) Configure Convergence to Use ISS

See Enabling Convergence and Indexing and Search Service.

  1. Configure Convergence to provide the ISS attachment interface.
    cd /opt/sun/comms/iwc/sbin
    ./iwcadmin -w <password> -o ISS.enable -v true
    ./iwcadmin -w <password> -o ISS.enablessl -v true (if SSL to be used)
    ./iwcadmin -w <password> -o ISS.host -v <ISS-web-frontend-FQDN>
    ./iwcadmin -w <password> -o ISS.port -v <ISS-web-frontend-port>
    ./iwcadmin -w <password> -o ISS.proxyadminid -v <value of ISS's mail.imap.admin.username>
    ./iwcadmin -w <password> -o ISS.proxyadminpwd -v <plaintext password for mail.imap.admin.username>
    

    ISS-web-frontend-port is the web component port number on which ISS is deployed (and should be the same as the port number for appserver.web.port in the jiss.conf file). Typically, the port number is 8080.
  2. If you are deploying Convergence and ISS on the same host and on the same GlassFish Server web container, you must increase the number of GlassFish Server request processing threads to two times the number of CPUs on the system.
    1. Determine the number of CPUs on the system.
      • Red Hat Linux:
        cat /proc/cpuinfo | grep processor | wc -l
        
      • Solaris OS:
        mpstat | grep -v CPU | wc -l
        
    2. Set the number of request processing threads to two times the number of CPUs determined above. If the number of CPUs is 4 or less, set this number to 8.
      cd /opt/SUNWappserver/bin
      ./asadmin set server.http-service.request-processing.thread-count = <2 x number-of-cpus>
      
  3. Restart GlassFish Server.
    cd /opt/SUNWappserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    

Uninstalling ISS

  1. To uninstall the Indexing and Search Service installed on the local machine, run the setup -u command, for example:
    # cd <iss-base>/bin
    # ./setup -b <iss-base> -u
    Logfile is: /var/tmp/jiss.install.13067
    No setup type found, defaulting to all
    Removing single-sign on
    Undeploying JISS wars to Appserver
    Stopping JISS services
    Removing Apache if required
    Removing up mq entries
    Removing up ldap entries
    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
    All configurations have been run successfully
    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
    
  2. If necessary, uninstall the Communications Suite packages.
    See Uninstalling Communications Suite for more information.

ISS Installation Command-Line Reference

Troubleshooting Indexing and Search Service Installation Problems

Initial ISS Troubleshooting

If you encounter problems during the initial ISS configuration, it might be helpful to run the setup uninstall, adjust the initial configuration, and re-attempt the setup. See setup Usage for more information.

Troubleshooting ISS Configuration Problems

This section describes how to troubleshoot installation problems without using the setup utility.

  1. Change to the iss-base/bin directory.
  2. Copy the example configuration file.
    cp ../etc/jiss.conf.example myfile.conf
    
  3. Edit the myfile.conf with your configuration details.
  4. Move the existing configuration files.
    mv ../etc/jiss.conf ../etc/jiss.conf.backup
    mv ../etc/jiss_passwd.conf ../etc/jiss_passwd.conf.backup
    
  5. Run the configure_etc.pl script to create new jiss.conf and jiss.password files.
    ./configure_etc.pl -c myfile.conf -A
    
  6. Run the verify_data.pl script to check the iss-base/etc/jiss.conf and iss-base/etc/jiss_passwd.conf files for all required parameters and formating.
    ./verify_data.pl
    
  7. Run the verify_conf.pl script to check if needed services are running and can be authenticated with provided credentials.
    ./verify_conf.pl
    
  8. If all these steps passed, run setup to configure the system.
    ./setup -b <iss-base>
    

See Indexing and Search Service Troubleshooting for more information.

Labels:
installationscenario installationscenario Delete
indexsearchservice indexsearchservice Delete
guide guide Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.