To determine whether the installation and initial configuration was successful, you need to start the Application Server.
See the following topics for details:
- Start the InterAction Application Server Service
- Displaying the Application Server Status Report
- Checking the Error Logs
- Stopping the Application Server Service
- Restarting the Application Server
Start the InterAction Application Server Service
Use the status report to determine whether Application Server is currently running. For details, see Displaying the Application Server Status Report.
-
If the Application Server is already running, stop it and delete the servlet engine log files.
This makes it easier to find the entries added during the restart, as opposed to older items in the log files.
See Stopping the Application Server Service and Restarting the Application Server.
- From the machine on which the Application Server is installed, access Services via Server Manager > Tools > Services.
- Double-click the Services application.
-
In the list of services, right-click InterAction Application Service and choose Start.
Once the server starts, the status for the server should change to Running.
-
Run the Application Server status reports to confirm that a browser can communicate with Application Server.
For details on the status report, see “Displaying the Application Server Status Report,” later.
Displaying the Application Server Status Report
You can use the Application Server status report to check that everything started correctly. You can view this report in your Web browser.
To access Application Server through a Web browser, enter the Application Server host name into a standard http:// address in your browser. For example, if your Application Server host name is IAServer1, the following address requests the status report:
http://IAServer1/InterAction/statusreport
Once the report appears in the browser, it should note that Application Server is running. For details about using and interpreting the Application Server administrative reports, see Administrative Reports for the Application Server.
Checking the Error Logs
If the Application Server did not start properly, you can check the error logs to help diagnose the problem. Interpreting the error logs is covered in detail in Log Files for the Application Server.
Stopping the Application Server Service
You may need to stop the Application Server when troubleshooting problems. To do so, follow these steps:
- From the machine on which the Application Server was installed, access Services via Server Manager > Tools > Services.
- In the list of services, right-click on InterAction Application Service and choose Stop.
-
If you are restarting the server, you may want to delete the servlet engine log files.
For details, see Restarting the Application Server.
Do not use the Restart feature in the Services utility. Stop the Application Server service and then Start it.
Restarting the Application Server
When restarting the server, it is useful to delete the servlet engine log files first. This makes it easier to find the entries added during the restart, as opposed to older items in the log files. You must stop the Application Server before you can delete the log files. The servlet engine log files have these filenames:
- InterAction-err.log
- InterAction-event.log
- InterAction-out.log
By default, the files are located in this location:
[Drive]:\Program Files\LexisNexis\InterAction\AppServer\logs
Delete all three files. Next time you start the Application Server, the files are recreated.