Now that you’ve installed Pro/INTRALINK, you have probably realized that to start the system running, you need to make sure that the database, the web server, the servlet engine and the Pro/INTRALINK Method Server all need to be running. Unfortunately, out of the box, this typically requires logging in and manually launching each of those applications.
In the Unix world, this is a fairly easily remedied by ensuring that the startup links are copied into the appropriate init directory. But in the Windows world, this requires that you set these applications up as Windows services.

In a typical installation, Oracle is already configured to automatically start up as a service. You may just want to ensure that the Oracle Listener is set to start automatically.Apache can be configured to start as a service by issuing the following command from the Apache home directory:

ant -f config.xml installService -DserviceName="ProI Apache"
Similarly, Tomcat requires the following command from its home directory:

ant -f config.xml installService -DJAVA_HOME=JDK_Path -DserviceName="ProI Tomcat" where JDK_Path is the fully qualified path to the Java SDK

And finally, the Pro/INTRALINK Method Server can be setup to run as a service by entering the following command from within the Windchill shell in the Windchill home directory:

ant -buildfile d:\ptc\Windchill\opt\ntservice\WindchillService.xml install -DserviceName="ProI 8 Server"

Unfortunately, running these applications as services eliminates the terminal windows that often provide detailed feedback or troubleshooting information, so it is best to enable these as services after you are sure that the system is working properly. In any case, you can still access the detailed information on these applications through their standard log files.

Hopefully this tip can help eliminate some of the extra burden on you, as administrators, when you have to reboot your servers. Let me know if you have any questions in the Administration Forum.