Page tree
Skip to end of metadata
Go to start of metadata

Successful completion of the installation process is only possible when database, network, and local configuration settings have been correctly set. Components should continue to run properly after installation as long as the environment remains unchanged and all external elements that Insight relies on remain intact, unchanged, and running.

Testing the Installation of the User Manager

Though you will likely implement the User Manager as a service, it is strongly recommended that you test User Manager in console mode first to make sure that it has been properly installed.

  1. Locate the "InsightUserManager" executable in the User Manager installation directory. If you installed with the default settings, you will find it in:


Table 6: Common Installation Locations for the Insight User Manager

Platform

Location

Windows

C:\program files\LunaImaging\5.x\user_manager|

Solaris / LINUX

/usr/home/insight/LunaImaging/5.x/user_manager/


  1. Launch it.


  1. A console window will open and begin a scroll of startup statistics. Toward the bottom of the scroll, look for the following line:


IUS: Accepting connection.
If you do not see this line, see the section labeled "Starting the User Manager in Console Mode" on page.
NOTE:Closing the console window will close the User Manager. Do not close the console window unless you want to close the User Manager.

Testing the Collection and Personal Insight Managers

Though the Collection Manager and Personal Insight Manager are distinct products, they may both be tested in the same way. They will both be referred to as "Managers" below.
To begin testing them:

  1. Locate the "InsightCollectionManager" executable in the Manager installation directory. If you installed with the default settings, you will find it in:


Table 7: Common Installation Locations for the Insight Collection Manager

Platform

Location

Windows

C:\program files\LunaImaging\5.x\collection_manager\xyz*

Solaris / LINUX

/usr/home/insight/LunaImaging/collection_manager/xyz*

 

  • where "xyz" is the short-name you defined for your collection


Table 8: Common Installation Locations for the Personal Insight Manager

Platform

Location

Windows

C:\program files\LunaImaging\5.x\personal_insight_manager\xyz*

Solaris / LINUX

/ usr/home/insight/LunaImaging/personal_insight_manager/xyz*

 

  • where "xyz" is the short-name you defined for Personal Insight


  1. Launch your Collection manager or Personal Insight Manager.


  1. A console window will open and begin a scroll of startup statistics. Toward the bottom of the scroll, look for the following line:


XYZ: Accepting connection.
(where "XYZ" is the short-name you defined for your collection)
If you do not see this line, see the section labeled "Starting the Collection Manager or Personal Insight Manager in Console Mode" on page .
NOTE: Closing the console window will close the Collection or Personal Insight Manager. Do not close the console window unless you want to close the Collection or Personal Insight Manager.

Starting Insight Studio

By starting Insight Studio on the server, you can test that your User Manager, Collection Manager, Personal Insight Manager, and Tomcat are working properly. Insight Studio is used to build collections and to configure Personal Insight.
NOTE:Your Collection Manager, Personal Insight Manager, User Manager must be running for Insight Studio to run properly.
NOTE:To test the media upload feature, you must also have Apache Tomcat running.
NOTE:Insight Studio is only available on Windows and Mac OSX You may need to install Insight Studio on a client machine to run these tests.
Testing the User Manager using Insight Studio:

  1. Locate the Insight Studio Application and double-click on "Insight Studio 6.3".


  1. If Insight Studio launches normally, you will see a login screen with a username / password.


  1. Use the Insight Admin username / password you specified in the installer.


  1. Click "login" when you've entered your password.


  1. If you can login, the User Manager is running properly. If not, please confirm your administrative username and password.


Testing the Collection Manager using Insight Studio:

  1. You should be presented with the Collection Manager you just installed. If you installed a Personal Insight Manager it should be listed as well.


  1. Double-click on the Collection Manager, and the folder should open with two options: "Create Catalog Template" and "Create a Collection", choose the latter.


  1. If you see the Insight Studio "Getting Started" panel (shown below), then you know that your Collection Manager is running properly.


  1. Repeat the steps above for the Personal Insight Manager.


NOTE: "Create a Collection" is not a Personal Insight option in Insight Studio. Insight Studio can create templates for Personal Insight, but cannot create Personal Collections.

Testing Apache Tomcat 5.0.19

Apache's Tomcat Application Server provides a platform for JSP and Servlet Applications for Insight. Tomcat commonly runs on port 8080 or 8081, and optionally also supports SSL connections by default on 8443.
To Test Tomcat:

  1. Locate Tomcat.


Locate the Tomcat installation directory. If you installed with the default settings, you will find it in: <see installation location>.
Table 9: Common Installation Locations for Tomcat

Platform

Location

Windows

C:\program files\LunaImaging\5.x\tomcat\bin

Solaris / LINUX

/ usr/home/insight/LunaImaging/tomcat/bin


  1. Start Tomcat.


Run "start_tomcat.bat" (Windows) or "start_tomcat.sh" (Solaris/Linux) from the Command Line (make sure it is not already running as a service!).

  1. Test that Tomcat is running.

Open a web browser. Go to http://localhost:8081/
NOTE: If you specified a different port for tomcat in the installer, replace 8081 with the appropriate port.
You should see the following page:

If you see anything other than the page above, check the Tomcat console for errors. Below is an example of the console output of a valid Tomcat startup:

Identifying Exceptions while watching the Tomcat Console

The most common error with Tomcat is that there is already a service running on Tomcat's port. On the console, you will see an error similar to this:
java.net.BindException: Address already in use: JVM_Bind:8081
If you already have something running on this port, you can change the port that Tomcat uses in Tomcat's server.xml configuration file.
NOTE: If you are running another version of Tomcat on the same machine, other ports supporting SSL, AJP, or J2K may also overlap and cause errors, please consult your server.xml for more information on changing these.
NOTE: The server install has configured many of Insight's components to use the port and hostname that you supplied in the installer, changing these after the fact will result in the manual re-configuration of the Collection Manager, Personal Insight Manager, Media Manager, BrowserInsight, and XML Gateway.

Testing the JPEG2000 Decoder & the Media Manager

To test the Media Manager, start Tomcat and open a web browser on the same machine.
NOTE: This testing document assumes that tests are run from the computer where Media Manager was installed, and is running Luna's distribution of Tomcat. If you are using your own version of Tomcat or using Resin, or are testing from another machine, you will have to adjust the tests.

Testing that the Media Manager is installed.


  1. In your browser, go to http://localhost:8081/MediaManager/. You should see a screen similar to Figure 5: Finding Media Manager Context in Tomcat below.
    1. If you do not see the page as displayed in Figure 5: Finding Media Manager Context in Tomcat below, the Media Manager servlet was not loaded.
      1. Check that the Media Manager was installed. It should be located in the media_manager directory of your Installation Directory.
      2. Check that the Media Manager Servlet Context file was installed. The "media_manager.xml" should be in conf/Catalina/localhost directory under the Tomcat installation directory.
      3. Open the "media_manager.xml" and confirm that the docBase parameter points to the media_manager/servlet directory above.


Figure 5: Finding Media Manager Context in Tomcat

An example of a failure to load properly:
Figure 6: Failure to find Media Manager Context in Tomcat

Testing the JPEG2000 Decoder:

  1. If the Media Manager page loaded successfully, go to http://localhost:8081/MediaManager/jp2ktest. You should see:

Figure 7: Successful Test of the JPEG2000 decoder

  1. If you see the error shown in Figure 8: Missing JPEG2000 Library Error below:
  2. Then it means that the JPEG2000 libraries are not accessible by Java. Check that the libraries are in the library path (specified above).
  3. Open the Insight installation directory.
  4. Navigate to the following directory:<installation_directory>/tomcat/common/lib

NOTE: This is the same location as ../common/lib in the example above.

  1. Check if the following libraries are in the common/lib directory, then add them (there are versions of the libraries in the <installation_directory>/media_manager/support directory separated by OS). If the libraries are there, check the rights to ensure that Tomcat has the ability to see them.


Figure 8: Missing JPEG2000 Library Error

  1. Go to http://localhost:8081/MediaManager/srvr. You should see the message below:

Figure 9: Media Manager Message with Ticketed Security Disabled

If you see the above message, then it means that the Media Manager is properly installed and is running.
If you have Media Security enabled you will see the message below:
Figure 10: Media Manager Message with Ticketed Security Enabled

  1. If media is not showing up in Insight, but the above tests show that the Media Manager is operational, the problem is likely in the Collection Manager's configuration. A few items to check:
  2. In Insight Administrator Tools or Insight Studio, check that the SPS values point to the Media Manager URL. See Error! Reference source not found. on page for more information.
  3. Do the private keys setup in the Media Manager and the Collection Manager match? See Error! Reference source not found. on page for more information.


Troubleshooting an Unsatisfied Link Error on Solaris

On Solaris, the JPEG2000 decoder requires common shared libraries to be installed in order to function properly. If these libraries are not installed, they may result in a java.lang.UnsatisfiedLinkError. For example:
java.lang.UnsatisfiedLinkError:/home/insight/Insight5.x/tomcat/common/lib/libkdu_v42R.so: ld.so.1: /home/insight/Insight5.x/jre/jre/bin/java: fatal: libstdc++.so.5: open failed: No such file or directory
This error is a result of missing libraries in /usr/local/lib. The tomcat sh script assumes the libgcc_s.so.1 and libstdc++.so.5 libraries exist in /usr/local/lib.
If you do not have copies of these libraries installed, you can find copies at:
<install_dir>/media_manager/support/Solaris-gcc/
To Install libgcc_s.so.1 and libstdc++.so.5:

  1. Copy libgcc_s.so.1 and libstdc++.so.5 to a common directory.


  1. Open the /tomcat/bin/tomcat_service.sh in a text editor.


  1. Locate the following Line:


LD_LIBRARY_PATH=/usr/local/lib

  1. Append the full path to the libraries to the end of the LD_LIBRARY_PATH with a colon separating the current and new path.


LD_LIBRARY_PATH=/usr/local/lib;/new/path

  1. Save the file and close it.


  1. Restart the tomcat service and go to http://localhost:8081/MediaManager/jp2ktest to verify that the error does not persist.


NOTE: Alternately, you can download the libgcc-3.3-sol8-sparc-local.gz package and install the libraries from http://www.sunfreeware.com/

Troubleshooting a Media File Compromised Error

One error with the Media Manager is that the base file path for media may be slightly different from the actual path. This most commonly occurs on Windows where file-paths are not case sensitive (while the Media Manager's checks are). If you see an error similar to the following, then check the MediaFileRootDir parameter.
Figure 11: Media File Compromised Error

To change the MediaFileRootDir property:

    1. Open your MediaManager.dat file (located in the media_manager directory) in a text editor.
    2. Find the MediaFileRootDir parameter.
    3. Check that the value matches the path to your media exactly (check the case of all pieces as well).
    4. Save the file.
    5. Restart Tomcat.

Testing your BrowserInsight Installation

  • BROWSER INSIGHT IS NO LONGER SUPPORTED BEYOND 6.2


Once you have modified the configuration files for Tomcat or Resin by adding the context for BrowserInsight, start Tomcat or Resin. By default, Tomcat and Resin are configured to run on Port 8081, to test that Resin or Tomcat is running properly:
Open a web Browser on the server running tomcat or resin and load the following page: http://localhost:8081

  1. Both Resin and Tomcat will display a default page stating that they are configured properly. If you do not see a page like this, check your configuration files for errors. There may be a missing "<" or ">". For other common configuration problems, review the Resin or Tomcat Manual.
  2. If the default page loaded properly, load the following page:

http://localhost:8081/BrowserInsight/BrowserInsight

  1. If Insight is configured properly, you should see a login page (below):
  2. Enter your administrative username and password.

If you have already built collections, then you can press login and select one.
If you are expecting to see collections, but cannot, then the next step is to enable BrowserInsight's debugging information.

Troubleshooting Collections not displaying in BrowserInsight

BrowserInsight will attempt to dynamically add new 5.x collections once they're created. To this end, there is one requirement for any collection, specifically, that there is already a collection in that database. If there is an existing collection in that database, BrowserInsight will dynamically add the collection once it's created. If you just added a new Collection Manager or Personal Insight Manager to your version of BrowserInsight, try restarting BrowserInsight once the collection has been created.
If your collection still is not showing in the select list, try increasing the debug level and watching the console text. For more information on increasing the debug level for BrowserInsight, please see Enabling Debug Information for BrowserInsight on page .

Testing the XML Gateway

Testing for proper installation and configuration of the Insight XML Gateway is a two-step process. Before testing the XML Gateway installation, please ensure that Tomcat or Resin is properly installed and is able to serve its standard web pages and servlets. The default URL for the XML Gateway is:
http://<ipaddress>:<port>/insight/servlet/XMLGateway
These instructions assume that a default installation of Tomcat/Resin is being used as the servlet container, though Tomcat is shown. The testing process using Resin is similar, but exact steps and screenshots will differ.
Out of the box, the 6.3 version of Insight was shipped with a "Gateway Tester" application which sends a "collection list" request to the XML Gateway and returns the result. (For more information on the different types of requests that Insight XML Gateway responds to, please see the XML Gateway Documentation.)

  1. Since the XML Gateway is middleware, it has no front-end. It can be tested by running a program that accesses it. A tester has been written for that purpose. Run the tester by going to the following location with your browser:

http://<ipaddress>:<port>/insight/servlet/tester
where <ipaddress> and <port> are those of the running Tomcat/Resin server. When Tomcat/Resin and the XML Gateway are properly configured, you should receive the following response:
Analyzing the messages above step by step:

  1. Connecting to gateway … (the tester is connecting to the XML Gateway).
  2. sending xml … (if you got this far, then the tester connected properly to the XML Gateway).
  3. waiting for response … (xml was sent to the Gateway).
  4. reading xslt… (received xml response, now processing).
  5. Transformer factory … (ignore).
  6. Transformer is (ignore).
  7. beginning xslt transform… (ignore).
  8. completed xslt … (check for errors below this line).


NOTE: The response status is 0 – meaning that the xml gateway is configured properly and was able to connect / communicate with the User Manager.
NOTE:Your list of collections will differ, based on collections made available to the XML Gateway.
NOTE: Each collection will also display a status message after it.
A successful test will return a response of 0 – similar to above.
Error codes will be accompanied by a message in the status box. It will display any configuration errors in the xml gateway's web.xml configuration file.
http://<ipaddress>:<port>/insight/servlet/XMLGateway

  • No labels