When running Tomcat versions after 8.0.11, you will find that Web Central does not start. The solution is that after deploying Web Central, you must delete the following files: (3045933)
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.
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:
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.
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.
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:8081/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.
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.
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.
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.
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:
afm-config.xml file. By default, the file is located in the WEB-INF\config\context\compatibility
folder.<language isoLanguage="fr" enabled="false" dbExtension="fr" />
If you are using the Sybase Runtime and get "metadata" errors
when loading View Analysis views, check your afm-projects.xml. It
is likely set to use the authoring or multi-user server project connection
(the jConnect driver) rather
than the Runtime (iAnywhere) driver. This happens when you connect via the afm-projects.xml information for a Sybase Runtime project (e.g. the "HQ-Sybase-Runtime" sample project) but are actually running the full Sybase Adaptive Server Anywhere server.
The ARCHIBUS Web Central install will set your
JAVA_HOME variable to the location of your JRE if it is not already set.
Neither application servers, like Tomcat, nor Web Central,
will run without this variable.
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:8081/archibus/schema/common/login.axvw).
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.
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:
If you continue to have difficulties, be sure to check that:
ai-licenses.bin and
afm-projects.xml files are present in the \webapps\archibus\WEB-INF\config
folder. JAVA_HOME environment
variable and that it is set to the location of your Java Runtime Environment.ping <servername>
or ping <server IP address>.c:\windows\system32\drivers\etc\hosts) has
an entry for:127.0.0.1 localhost
\webapps\archibus\WEB-INF\log\archibus.log) does not show any errors.| Copyright © 1984-2015, ARCHIBUS, Inc. All rights reserved. |