Tomcat Web Application Server Does Not Start

If Tomcat does not start (for example, there are a series of errors in the Tomcat window and Tomcat does not display a message such as “Apache Tomcat/5.5.9”), make certain you have started the HQ Headquarters project before you start Tomcat.  If Tomcat still does not start, check the contents of \afmxx\tools\tomcat\webapps\archibus\web-inf\log\archibus.log for other information.

Tomcat Web Application Server Takes a Long Time to Start

The first time you start Tomcat after installing FM Web Central, Tomcat may take several minutes to expand the archibus.war file. Do not stop Tomcat or shutdown Tomcat until the .war file is completely expanded.

If Tomcat cannot expand the archibus.war file, check to see if the folder C:\Program Files\Afmxx\tools\tomcat\webapps\archibus exists. If so:

1. Back up any files in this folder (typically those in the \archibus\schema\per-site folder) that you want to save.
2. Delete the \archibus folder and its contents.
3. Start Tomcat to expand the archibus.war file.
4. After the .war file has been expanded, copy the backup files to the C:\Program Files\Afmxx\tools\tomcat\webapps\archibus folder.

Two Versions of Tomcat

If you have two versions of Tomcat loaded on your computer, and one will not start, make certain the other version  is completely shut down or uninstalled, as the two versions can conflict.

Service Form of Tomcat

If you are running Tomcat as a service, you may need  to reboot your computer after you install. This resolves problems of installing newer versions of Tomcat on some workstations.

Port Number is In Use

If port 8080 is in use, Tomcat will not start. This can happen if another application, such as a database or another Web service, is using this logical port. This can also happen if you already have a copy of Tomcat (perhaps another version) running as a service.

You can use the "netstat" command ("netstat -ln" on Linux) to list ports in use. You can also try to telnet to that port ("telnet localhost 8080"). If the connection succeeds, there is a service on that port; use the get command ("GET /") to list which service this is.

To change the port number, edit the \ tomcat\conf\server.xml file; search for "port =8080" (this will be inside a <Connector /> tag) and change it to another number (e.g. "8081"). "Next", change your login URL accordingly (e.g. http://localhost:808 1 /archibus/schema/common/login.axvw ).

Also be certain to change the absoluteAppPath in the \webapps\archibus\WEB-INF\config\context\compatibility\afm-config.xml file.

Requested Resource Unavailable

If you get either a "404" error or the above message when logging in, check if "Archibus" is spelled all lower- case in your URL: for instance, http://harp:8080/archibus/login.axvw will work but http://harp:8080/Archibus/login.axvw will not.

Database Not Started

If the Archibus database is not started -- or in fact, if any database connection in afm-projects.xml is not started -- your application server has started, but the Web Central application itself has not. You will be able to tell that Web Central is not starting because the "ConfigManager" in Web Central will not display any messages to your application server console window; and you will not be able to log in.

To remedy this situation, stop the application server, start your database or databases, and then restart the application server.

Wrong Database Version

If you have a version of the database running on you database server that is of an earlier format than the database version shipped with the current Archibus, then your application server will start, but you will get a series of "Severe" warnings in the console window.

Update your database to the latest format using the Database Update Wizard, and try again. If you wish to verify that you have a database version issue, as opposed to another problem, start the Archibus Web Central application with the sample Headquarters (HQ) database instead.

Double-byte Languages and Microsoft SQL Server

If you are using a double-byte language (Chinese or Korean) and you are using Microsoft SQL Server, disable languages other than English before starting Web Central. To disable a language:

1. Open the afm-config.xml file. By default, the file is located in the \WEB-INF\config\context\compatibility folder.
2. Search for the <languages> tag and the language(s) you need to disable.
3. Disable the language by changing the enabled value to false . For example:

<language  isoLanguage="fr" enabled=" false " dbExtension="fr" />

Port 8080 In Use

Port 8080 may already be in use on your computer by a database or another Web service.  Edit the tomcat\conf\server.xml file; search for port “8080” and change it to another number (e.g. “8081”).  Next, change your login URL accordingly (e.g. http://localhost:808 1 /archibus/schema/common/login.axvw ).

Requested Resource Unavailable

Check if "archibus" is spelled all-lower case in your URL: for instance, http://harp:8080/archibus/login.axvw will work but http://harp:8080/ARCHIBUS/login.axvw will not.

Proxy Server Blocking Access

If you have a proxy set up for all HTTP services, it may be blocking access even to a local server. To remedy this situation:

• Use the Tools/Internet Options/Connections tab; select the Advanced button; enter localhost and 127.0.0.1 (or your server information) in the Exceptions box.

If you continue to have difficulties, be sure to check that:

• The ai-licenses.bin and afm-projects.xml files are present in the \webapps\archibus\WEB-INF\config folder.
• You have a JAVA_HOME environment variable and that it is set to the location of your Java Runtime Environment.
• If you are logging in remotely, that you can access the host computer by using ping <servername> or ping <server IP address> .
• If you are logging in locally, that your hosts file (e.g. c:\windows\system32\drivers\etc\hosts ) has an entry for:

127.0.0.1 localhost

• Your Web Central log file ( \webapps\archibus\WEB-INF\log\archibus.log ) does not show any errors.