1 Reply Latest reply: Jul 16, 2013 12:42 PM by JimKlimov RSS

    Oracle Communication Suite 7u4 installation fails during ISS service setup

    user13484556

      Hi all,

      While installing oracle communication Suite Indexing and Search service i getting following error.

      My glassfish server is Sun GlassFish Enterprise Server v2.1.1 Patch20 ((v2.1 Patch26)(9.1_02 Patch32)) (build b02-p20)

      ####################################################################################

      root@mail # ./setup -O

      Log file is /var/tmp/jiss.install.13430

      No mode provided, defaulting to install

      Mode is install

      Type(s) is ldap jmq web index cluster watcher all

      Reading defaults from /opt/sun/comms/jiss/bin/..//etc/jiss.conf.template

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Cluster information for ISS services

      Starting section: cluster

          Cluster configuration, multi-machine, cluster, clusterv2, or standalone

          (iss.cluster.install) [standalone]:

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Local Install Settings

      Starting section: jiss

          Fully qualified domain name of this system (hostname) [none]: mail.iitr.ac.in

          Instance name of the installation for an indexing node, ie iss1.

          (instance.name) [none]: iss1

          User under which all JISS services will run (iss.user) [jiss]:

          Group under which all JISS services will run (iss.group) [jiss]:

          Location to store the Lucene indexes (iss.store.dir)

          [/var/opt/sun/comms/jiss/index]:

          Location of attachment data (iss.data.dir)

          [/var/opt/sun/comms/jiss/attach]:

          Location of JISS log files (iss.log.dir)

          [/var/opt/sun/comms/jiss/logs]:

          Location of Java (java.home) [/usr/jdk/latest]:

      Verifying section: jiss

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Message Store Configuration

      Starting section: ms

          User/Group Directory Server; format:

          host.example.com:389,host2.example.com:389 (mail.ldap) [none]: ldap.iitr.ac.in:389

          User/Group Default Domain (mail.defaultdomain) [none]: iitr.ac.in

          User/Group Directory Manager DN (mail.searchbind) [cn=Directory

          manager]:

          User/Group Directory Manager password (mail.searchbind.password)

          [none]:

          Enter password again:

          Messaging Server store hostname (local.hostname in Messaging Server)

          (mail.server) [none]: store.iitr.ac.in

          Comma-delimited list of IP addresses corresponding to mail.server

          (particularly the interface connecting to ISS) (mail.server.ip) [none]: 192.168.180.11

          Read-only store admin username (store.indexeradmins in Messaging

          Server) (mail.imap.admin.username) [indexeradmin]:

          Read-only store admin password (mail.imap.admin.password) [none]:

          Enter password again:

          Messaging Server IMAP port (mail.imap.port) [143]:

          Messaging Server JMQ broker; format: host.example.com:7676 (mail.imq)

          [none]: mail.iitr.ac.in:7676

          JMQ notification user (must match

          local.store.notifyplugin.index.jmquser in configutil) (mail.imq.user)

          [jmquser]:

          JMQ notification user's password (must match

          local.store.notifyplugin.index.jmqpwd in configutil)

          (mail.imq.password) [none]:

          Enter password again:

      Verifying section: ms

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Application Server Settings

      Starting section: web

          Directory location of the appserver (appserv.dir) [/opt/SUNWappserver]:

          Appserver web port (appserv.web.port) [8080]: 80

          Appserver admin port (appserv.admin.port) [4848]:

          Appserver domain name for deployment (appserv.domain) [domain1]:

          Appserver admin user (appserv.admin.user) [admin]:

          Appserver admin password (appserv.admin.password) [none]:

          Enter password again:

          Deploy the SearchUI web application used for testing and debugging

          (appserv.searchui.enabled) [false]: true

      Verifying section: web

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Java Message Queue Settings

      Starting section: jmq

          JISS JMQ broker hostname(s) list, ie host:7676,host2:7677 (imq.host)

          [none]: mail.iitr.ac.in:7676

          Username for JISS JMQ broker (iss.imq.user) [jmquser]:

          Password for JISS JMQ user (iss.imq.password) [none]:

          Enter password again:

          Password for admin user on JISS JMQ broker (iss.imq.admin.password)

          [none]:

          Enter password again:

      Verifying section: jmq

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Directory Server Configuration for JNDI

      Starting section: ldap

          File based or Directory Server based JNDI lookups, file or ldap

          (jndi.type) [none]: ldap

          JISS Directory Server host list host:port,host2:port2 (ldap.host)

          [none]: ldap.iitr.ac.in:389

          JISS Directory Manager DN; format: cn=Directory Manager

          (java.naming.security.principal) [cn=Directory Manager]:

          JISS Directory Server password (ldap.password) [none]:

          Enter password again:

      Verifying section: ldap

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Run time configurations for ISS services.

      Starting section: service

          Storeui access method, disk for single machine, http for multi-machine

          (iss.storeui.access.method) [disk]:

      Verifying section: service

      This section has passed verification

      =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

      Watcher service configurations.

      Starting section: watcher

          Watcher service enabled on this host (iss.watcher.enabled) [false]:

      Verifying section: watcher

      This section has passed verification

      Verifying section: undocumented

      This section has passed verification

      Setting up ldap configuration

      Setting up jmq user

      Setting up jmq configuration

      Starting JISS services

      Checking if Apache is required

      Setup single-sign on

      ERROR: Could not setup Single Sign On

      output: No object matches the specified name "server.http-service.virtual-server.server.property.sso-enabled"

      CLI137 Command set failed.

      Error running /opt/SUNWappserver/bin/asadmin set --user admin --passwordfile=/opt/sun/comms/jiss/etc/.appserv_pass.19010 --port 4848 server.http-service.virtual-server.server.property.sso-enabled=true

       

       

      root@mail #

      #########################################################################################

      regards

      Sumit Samaddar

        • 1. Re: Oracle Communication Suite 7u4 installation fails during ISS service setup
          JimKlimov

          I have an older setup here, but it has the SSO options set properly. So, generic troubleshooting:

           

          Can you set (or get) this option in command-line, without the installer?

          Can you set (or get) it in the admin web-GUI?

           

          From the looks of it, one reason may be that your virtual HTTP server used for CommSuite was renamed and is no longer the default "sever"?
          You can also look if there are matching options in the appserver config file, i.e.:

           

          # ggrep -A3 -B3 sso-enabled /opt/SUNWappserver/domains/domain1/config/domain.xml

          ...

                  <virtual-server hosts="${com.sun.aas.hostName},ucs.mydomain.com"

                            http-listeners="http-listener-1,http-listener-2" id="server"

                            log-file="${com.sun.aas.instanceRoot}/logs/server-server.log" state="on">

                    <property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>

                    <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>

                    <property name="sso-enabled" value="true"/>

                  </virtual-server>

          ...

           

          HTH,

          //Jim