After installing Platform Services, you may need to start the HTTP Service.
On Windows, the HTTP Service (if installed) is automatically started when the computer reboots after the installation is complete.
On UNIX, the service can be started either from the command line or init from
inittab.
See the next topic for details on starting the service from
inittab.
In a UNIX production environment, the HTTP Service can be started by init from inittab.
In a UNIX development environment, the HTTP Service can be started from the command
line. In a UNIX production environment, however, Oracle recommends that it be started by init from
inittab.
If the service crashes or is terminated, init automatically restarts it.
The UNIX version of Platform Services contains a file named endeca_run.sh that is in the $ENDECA_ROOT/tools/server/bin directory. This is a version of startup.sh that calls run
instead of start and redirects stdout and stderr to
$ENDECA_CONF/logs/catalina.out.
You can write a script that is referenced in inittab. The script sets environment variables and then
calls endeca_run.sh. When writing your script, it is recommended as a best practice that you run
the HTTP Service as a user other than root. When running the service as a non-root user, you
can set a USER environment variable that will be inherited by other scripts, such as EAC scripts.
This sample script (named start_endeca_http_service.sh) sets the ENDECA_USER variable
to the "endeca" user, sets the INSTALLER_SH variable to the path of the environment variables script
and sources it, and then does an su to change to the "endeca" user:
#!/bin/sh ENDECA_USER=endeca INSTALLER_SH=/usr/local/endeca/PlatformServices/workspace/setup/installer_sh.ini # We want to use installer_sh.ini variables in this script, # so we source it here. source $INSTALLER_SH # change to user endeca su $ENDECA_USER -c "/bin/sh -c \"source $INSTALLER_SH; \ cd $ENDECA_CONF/work; exec env USER=$ENDECA_USER \ $ENDECA_ROOT/tools/server/bin/endeca_run.sh\""
On Solaris platforms, replace "source" with "." because source is not a command in the Bourne shell.
The start_endeca_http_service.sh script is then referenced in inittab with an entry similar
to this example.
ec:2345:respawn:/usr/local/endeca/PlatformServices/workspace/setup/start_endeca_http_service.sh
When writing your startup script, keep in mind that it is server-specific, and therefore its details (such as paths and user names) depend on the configuration of your server.
