This topic provides an overview of the recommended way to run IAS components, optional ways to run IAS components, and explains differences between Windows and UNIX platforms.
As discussed in the introduction, the Endeca IAS Service is a container process that runs the IAS components such as the IAS Server, the Component Instance Manager, and one or more Record Store instances. In a typical implementation, running the IAS Service is the recommended way to run IAS components.
Each utility is described in this guide.
On Windows, the Endeca IAS Service is automatically started as part of the installation process. Oracle recommends that you start and stop the service from the Microsoft Services console.
You may optionally choose to start the Endeca IAS Service on Windows using the ias-service.bat script in <install path>\IAS\<version>\bin, and stop it using ias-service-shutdown.bat.
On UNIX, you run the Endeca IAS Service using the scripts in <install path>/IAS/<version>/bin. You start the service with ias-service.sh or via the inittab, and stop it with ias-service-shutdown.sh. Oracle recommends using the inittab in production environments.
On either platform, you can leave the service running as a background process. The only time you must restart the service is if you modify any of the configuration files in <install path>\IAS\<version>\conf. For example, you might change the IAS Service logging configuration and therefore have to restart the service.