Indexing and Search Service Initial Configuration

Skip to end of metadata
Go to start of metadata

< Back to Communications Suite 7 Update 1 Installation Scenario - Indexing and Search Service

What You Need to Do Before Performing Indexing and Search Service 1 Update 1 Initial Configuration


In Communications Suite terminology, initial configuration is not the same as initial installation. Thus, before using the information on this page, make sure that you have completed all the prerequisite steps. If you have come to this page to start your ISS 1u1 installation, instead start with the instructions in Installation Scenario - Indexing and Search Service.

Indexing and Search Service for Oracle Communications Unified Communications Suite Installation Initial Configuration
Version 1 Update 2

After you install the Indexing and Search Search software by using the Communications Suite installer, you must configure the components to complete the installation. You perform this initial runtime configuration by running the Indexing and Search Service configuration program, setup.

Topics:

Running setup

Generating a Configuration File

The configuration utility generates configuration files required to run the indexing services. The utility uses iss-base/etc/jiss.conf.template for default values but you are prompted for answers to various configuration questions about the Messaging Server messaging store install and the local system services.

Local Parameters

These parameters are used to configure local system settings.

Parameter Description Example Setting
hostname The host name for this Indexing and Search Service system. You must provide a fully qualified domain name. isshost.example.com
iss.user The user under which all ISS services will run. jiss
iss.group The group under which all ISS services will run. jiss
iss.store.dir Location to store the Lucene indexes. /var/opt/sun/comms/jiss/index
iss.data.dir Location of attachment data. /var/opt/sun/comms/jiss/attach
iss.log.dir Location of ISS log files. /var/opt/sun/comms/jiss/logs
java.home Location of Java software. /usr/jdk/latest
Message Store Parameters

These parameters are used to contact and operate with the Messaging Server message store.

Parameter Description Example Setting
mail.ldap User/Group Directory Server host.example.com:389
mail.basedn User/Group base DN dc=example,dc=com
mail.schemalevel User/Group Schema Level 2
mail.defaultdomain User/Group default domain example.com
mail.searchbind User/Group Directory Manager DN cn=Directory manager
mail.searchbind.password User/Group Directory Manager password dmpassword
mail.server The fully qualified domain name of the default Messaging Server that will be indexed mailhost.example.com
mail.server.ip Comma-delimited list of backend IPs corresponding to mail.server 10.0.0.1,10.0.0.2
mail.imap.admin.username Messaging Server read-only store administrator user name (defined with the store.indexeradmins configutil parameter) indexeradmin
mail.imap.admin.password Messaging Server read-only store administrator password changeme
mail.imq Message Queue broker hostname:port for Messaging Server JMQ notifications mailhost.example.com:7676
mail.imq.user User name for Messaging Server JMQ notifications (must match local.store.notifyplugin.index.jmquser in configutil) jmquser
mail.imq.password Password for Messaging Server JMQ notifications (must match local.store.notifyplugin.index.jmqpwd in configutil) changeme
GlassFish Application Server Parameters

These parameters are used to configure and deploy the .war file to GlassFish.

Parameter Description Example Setting
appserv.dir Location of the appserver directory /opt/SUNWappserver
appserv.admin.port GlassFish admin port 4848
appserv.web.port GlassFish web port 8080
appserv.admin.user GlassFish admin user admin
appserv.admin.password GlassFish admin user's password changeme
GlassFish Message Queue (JMQ) Service Parameters

These parameters contain information about accessing the GlassFish Message Queue.

Parameter Description Example
imq.host ISS JMQ broker host name jmq.example.com
imq.port ISS JMQ broker port 7676
iss.imq.user User name for ISS JMQ broker misoadmin
iss.imq.password Password for ISS JMQ user changeme
iss.imq.admin.password Password for admin user on ISS JMQ broker admin
Directory Service Parameters

These parameters contain information about connecting to directory services that hold the Java Naming and Directory Interface (JNDI) lookup.

Parameter Description Example Setting
ldap ISS Directory Server host ldap.example.com
ldap.port ISS Directory Server port 389
java.naming.security.principal ISS Directory Manager DN cn=Directory Manager
ldap.password ISS Directory Server password changeme
ISS Services Parameters

This section contains ISS services configuration.

Parameter Description Example Setting
iss.storeui.access.method Storeui access method. Use disk for a single host environment, or http for a multi-host environment disk

Examples

# cd <iss-base>/bin
# ./setup -b /opt/sun/comms/jiss/ 
# ./setup -b /opt/sun/comms/jiss/ -c my.conf (for silent mode configuration)

Using setup in a Multi-host Environment

For more information on ISS multi-host deployment planning, see ISS Logical Architecture.

Using a Default Configuration File

All machines in the environment should have the same configuration. You should create your configuration ahead of time by using a copy of the iss-base/etc/jiss.conf.example file. If you concatenate the jiss.conf and jiss_passwd.conf files to generate the configuration that you will use on all hosts, then before doing so, you must update all the passwords in the configuration to plain text.

The iss.storeui.access.method Parameter

In a multi-machine deployment, if the application server and the index reside on different hosts, you must set up an Apache server on the indexing host to provide access to the attachment store to the application server. This Apache server runs under the iss.user and iss.group credentials.

Storeui access method, disk for single machine, http for multi-machine [disk]: http

Install Order

Run the setup utility in the following order for multi-machine installs:

  • ldap - Holds JNDI lookups
  • ms - Message store configuration
  • jmq - Requires JNDI lookups
  • index - Requires JNDI lookup and GlassFish Message Queue
  • web - Requires index services to be started

When using an ISS host to perform the Directory Server function for JNDI lookups, you run the setup ldap command on the ISS host, not on the Directory Server host (which typically serves your entire deployment). This enables the external Directory Server to host JISS's JDNI lookups. The ISS host that you use to run the command must have access to the ldapmodify and ldapsearch binaries.

Example 1

This example describes a three-machine setup for JISS:

  • web.example.com - Application server (web)
  • middle.example.com - Directory service and GlassFish Message Queue (ldap, jmq)
  • index.example.com - JISS Indexing services (index)

The first time that setup is run on each machine, you must provide the -c <CONF_FILE> and -i <FQDN> options. Once jiss.conf and jiss_passwd.conf are configured, these options can be omitted.

Run the following commands on middle.example.com:

# <iss-base>/bin/setup -t ldap -c my.conf -i middle.example.com
# <iss-base>/bin/setup -t ms
# <iss-base>/bin/setup -t jmq 

Run the following commands on index.example.com:

# <iss-base>/bin/setup -t index -c my.conf -i index.example.com

Run the following commands on web.example.com:

# <iss-base>/setup -t web -c my.conf -i web.example.com

Example 2

This example describes a two-machine setup for JISS:

  • web.example.com - Application server (web)
  • index.example.com - JISS Indexing services, Directory service, and GlassFish Message Queue (index, ldap, jmq)

The first time setup is run on each machine, you must provide the -c <CONF_FILE> and -i <FQDN> options. Once jiss.conf and jiss_passwd.conf are configured, these options can be omitted.

Run the following commands on index.example.com:

# <iss-base>/bin/setup -t ldap -c my.conf -i index.example.com
# <iss-base>/bin/setup -t ms 
# <iss-base>/bin/setup -t jmq 
# <iss-base>/bin/setup -t index 

Run the following commands on web.example.com:

# <iss-base>/setup -t web -c my.conf -i web.example.com

Example 3

This example describes another three-machine setup for JISS:

  • web.example.com - Application server (web)
  • index1.example.com - JISS Indexing services (index), Directory service, and GlassFish Message Queue (ldap, jmq)
  • index2.example.com - JISS Indexing services (index)

The first time setup is run on each machine, you must provide the -c <CONF_FILE> and -i <FQDN> options. Once jiss.conf and jiss_passwd.conf are configured, these options can be omitted.

Run the following commands on index1.example.com:

# <iss-base>/bin/setup -t ldap -c my.conf -i index1.example.com
# <iss-base>/bin/setup -t ms 
# <iss-base>/bin/setup -t jmq 
# <iss-base>/bin/setup -t index

Run the following commands on index2.example.com:

# <iss-base>/bin/setup -t index -c my.conf -i index2.example.com

Run the following commands on web.example.com:

# <iss-base>/setup -t web -c my.conf -i web.example.com

Additional Indexing Node Configuration

The Apache server must be configured to respond to requests from the web nodes' IP addresses. The default is deny. You can add and remove additional hosts by using the configure_web_node utility. The IP address(es) should be the IP address(es) of the hosts running the application server(s).

Add an IP address:

# <iss-base>/bin/configure_web_node -a 10.10.10.10

Remove an IP address:

# <iss-base>/bin/configure_web_node -d 10.10.10.10

Add multiple IP addresses:

# <iss-base>/bin/configure_web_node -a 10.10.10.10 10.10.10.11 10.10.10.12
Labels:
indexsearchservice indexsearchservice Delete
guide guide Delete
configuring configuring 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.