wiki:Support/CommonProbsSolns
Last modified 3 years ago Last modified on 04/16/14 10:53:35

Common Problems and Solutions

  1. MSI won't install because you're not an administrator
  2. Missing java keystore and public key in keys/ directory of ICA/MUA/Web
  3. RPM won't install because it can't find java
  4. Can not resolve XML Schema files, raptor-mua startup problems


MSI won't install because you're not an administrator

Firstly - does your account actually have Administrator privileges? If not, then use one. If it does, and you're using a non-server version of Windows (e.g. Windows 7), then MSIs don't get executed with Admin privileges even if your account has them, so you'll need to do the following:

  • Click on start, type "cmd" in the search box, and it will appear at the top of the search list.
  • Right click on cmd, choose "run as administrator". This will give you a command prompt with real admin privileges.
  • Change directory to wherever you downloaded the MSI (e.g. cd \Users\YourUsername\Desktop).
  • type "msi /i nameof.msi" (that’s an "i" (for install) after the slash).

Missing java keystore and public key in keys/ directory of ICA/MUA/Web

If the only file in the keys/ directory of your ICA/MUA/Web is authorised-keys.jks, then the automatic key generation has failed and you will need to perform this manually.

  • On Linux
    • Note that you may need to use the full path to the keytool command if it is not in your path - it'll be located in your JRE's bin directory
    • For the ICA:
      # keytool -genkey -alias raptorica -keystore /opt/raptor/ica/keys/raptor-ica.jks -storepass changeit -keypass changeit -dname "CN=`hostname -f `,ou=ICA,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptorica -keystore /opt/raptor/ica/keys/raptor-ica.jks -storepass changeit -file /opt/raptor/ica/keys/raptor-ica-public.crt
      
    • For the MUA:
      # keytool -genkey -alias raptormua -keystore /opt/raptor/mua/keys/raptor-mua.jks -storepass changeit -keypass changeit -dname "CN=`hostname -f `,ou=MUA,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptormua -keystore /opt/raptor/mua/keys/raptor-mua.jks -storepass changeit -file /opt/raptor/mua/keys/raptor-mua-public.crt
      
    • For the Web:
      # keytool -genkey -alias raptorweb -keystore /opt/raptor/web/keys/raptor-web -storepass changeit -keypass changeit -dname "CN=`hostname -f `,ou=WEB,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptorweb -keystore /opt/raptor/web/keys/raptor-web.jks -storepass changeit -file /opt/raptor/web/keys/raptor-web-public.crt
      
  • On Windows
    • Note that you may need to use the full path to the keytool command if it is not in your path - it'll be located in your JRE's bin directory
    • For the ICA:
      # keytool -genkey -alias raptorica -keystore "C:\Program Files\Raptor\ICA\keys\raptor-ica.jks" -storepass changeit -keypass changeit -dname "CN=[INSERT YOUR HOSTNAME HERE],ou=ICA,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptorica -keystore "C:\Program Files\Raptor\ICA\keys\raptor-ica.jks" -storepass changeit -file "C:\Program Files\Raptor\ICA\keys\raptor-ica-public.crt"
      
    • For the MUA:
      # keytool -genkey -alias raptorica -keystore "C:\Program Files\Raptor\MUA\keys\raptor-mua.jks" -storepass changeit -keypass changeit -dname "CN=[INSERT YOUR HOSTNAME HERE],ou=MUA,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptorica -keystore "C:\Program Files\Raptor\MUA\keys\raptor-mua.jks" -storepass changeit -file "C:\Program Files\Raptor\ICA\keys\raptor-mua-public.crt"
      
    • For the Web:
      # keytool -genkey -alias raptorica -keystore "C:\Program Files\Raptor\Web\keys\raptor-web.jks" -storepass changeit -keypass changeit -dname "CN=[INSERT YOUR HOSTNAME HERE],ou=Web,o=Raptor" -validity 7300 -keyalg RSA -keysize 2048
      # keytool -export -alias raptorica -keystore "C:\Program Files\Raptor\Web\keys\raptor-web.jks" -storepass changeit -file "C:\Program Files\Raptor\ICA\keys\raptor-mua-public.crt"
      

RPM won't install because it can't find java

If you can't install any of the components because RPM/Yum can't find a Java install on your system, but one is definitely installed (probably manually), then you can work around the problem by doing the following:

  • When using yum:
    yum install -force <package>
    
  • When using zypper:
    zypper install -force <package>
    
  • When using RPM directly
    rpm -i --nodeps <RPM>
    

Can not resolve XML Schema files, raptor-mua startup problems

If your raptor-mua instance does not start due to a ' Could not parse mapping document from input stream' exception, the server the raptor-mua is located on can not reach the various XML schema files e.g. the core Spring schema is located at http://www.springframework.org/schema/beans/spring-beans.xsd. To fix schema references, for each /conf/*.xml file , each schema reference must be changed from a remote location to a local location. To do this, follow these steps:

  1. First, you must download the complete set of Schema files used by the XML config files (see table below for current list) into the conf/ directory (although they could be located anywhere on the local file system).
Component Schema
MUAhttp://www.springframework.org/schema/beans/spring-beans.xsd
MUAhttp://cxf.apache.org/schemas/jaxws.xsd
  1. Then, each schema reference in each of the XML files must be manually changed to reference the local file. Firstly, locate the xsi:schemaLocation element at the top of each XML file, then for each reference to a schema URL (the one that ends .xsd, not the namespace URI which should remain the same), replace the HTTP URL with the location of the XSD on your filesystem e.g. using file:///opt/raptor/mua/conf/spring-beans.xsd. For example, in the mua-core.xml file, the following changes to the xsi:schemaLocation element are made:

From

<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:jaxws="http://cxf.apache.org/jaxws"
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
        http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">

To

<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:jaxws="http://cxf.apache.org/jaxws"
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans file:///opt/raptor/mua/conf/spring-beans.xsd
        http://cxf.apache.org/jaxws file:///opt/raptor/mua/conf/jaxws.xsd">

Of note, upgrades to your Raptor installation will break some of these schema references as core files are overwritten. With this in mind, we are currently investigating how to configure a HTTP Proxy within Raptor.