Bookshelf Home | Contents | Index | Search | PDF

Siebel Analytics Installation and Configuration Guide > Installing Siebel Analytics Software in the UNIX Environment > Installing and Configuring Siebel Analytics Components >

After Installing the Siebel Analytics Server

---

After the installation, test the setup.

To test the Siebel Analytics Server installation

1. Run Siebel Analytics Client by opening another session. From the setup directory
   $INSTALLDIR/setup, run one of the following scripts:
   • If you are using sh or bash, run:

   . sa-cli.sh

   • If you are using csh, run:

   source sa-cli.csh

   To test the client/server connectivity, run:

   nqcmd.exe

2. Make sure all clients are disconnected from the Siebel Analytics Server, and then stop the server.
   • If you are using sh or bash:

   run-sa.sh { start | {stop -d <data source name> -u <user name> -p <password>} }

   • If you are using csh:

   run-sa.csh { start | {stop -d <data source name> -u <user name> -p <password>} }

   For example:

   run-sa.csh stop -d AnalyticsWeb -u Administrator -p SADMIN

   • If you have set up your environment with sa.sh or sa.csh:

   nqsshutdown.exe -d <data source name> -u administrator -p <password>

   NOTE:  If the password is empty, enclose it in double quotes ("").

If the Siebel Analytics Server Fails to Start

If the startup operation fails, look in the following log files for messages indicating possible reasons.

• NQServer.log file, located in the Log subdirectory in the Siebel Analytics software installation directory. You can use a text editor to view this file. (Set your viewer to UTF-8 to avoid seeing garbled text.)
• Run /usr/sbin/syslogd and look for any system and/or Siebel Analytics Server-related messages.

The log files contain messages indicating why the server startup failed. For example, if there were a syntax error in the NQSConfig.INI file, both the operating system's log and the NQServer.log file would contain messages about the syntax error. After examining the log messages, correct the problem and start the server again.

Bookshelf Home | Contents | Index | Search | PDF