SSPR upgrade - tomcat upgrade

I need to upgrade SSPR 3.0.0.1 to version 4.1.x. SSPR 4.1.x, which requires tomcat 8 or later and the current tomcat version being used in tomcat 7.
1. How can I make the tomcat upgrade, if you can please detail the steps ?
2. During upgrade can I somehow have the provision to keep the older deployment and switch back (fall back) to the previous SSPR deployment on older tomcat by making minor changes in case there are issues with the new deployment? If possible, how can I get this done.

Thanks!
  • Yikes; that is an old version. I would probably do the following, as I
    believe this is outside of a supported upgrade (though I think it SHOULD
    work, but let's be appropriate careful).

    1. Backup your SSPRConfiguration.xml file if you do not already
    often/regularly.
    2. Backup your database, wherever that is. Hopefully this is also done
    automatically, but of course you should have one that is current.

    3. Apache Tomcat stuff:
    Depending on your installation environment, I presume that Apache Tomcat
    is the one that came with Linux, and usually a new version comes with a
    new major release, so build a new box with a current version of SUSE Linux
    Enterprise Server (SLES) 12 SP3 and you will have the right Tomcat
    version. You may need to configure it to use a Sun/Oracle JDK instead of
    IBM or OpenJDK stuff, depending on what comes with it, but that's easy to do.

    4. Use the installation documentation to drop the WAR into the 'webapps'
    directory for Apache Tomcat like you did before with your old install.
    Import your SSPRConfiguration.xml file, which should also tell the system
    to point to your relational database.
    5. Test test test.
    6. Configure DNS/IP/etc. to point to the new box and eventually
    decommission the old box.

    With a new box built, you should be able to easily rollback to the
    previous version by just using the old system, assuming you do not change
    something in the database with the new version in a way that hurts the old
    install, but following Step #2 you at least have a backup that you can
    easily restore to get everything back to normal.

    In my experience, SSPR has been very tolerant of upgrades, meaning they
    are pretty smooth, but as these data are critical and user-facing having a
    backup and rollback strategy is also a good idea.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
  • So, this is what I did on another machine (where IDM/eDir is already installed)
    1.Placed tomcat 8.5 (tomcat 7 that comes with novell is already there).
    2.Installed java (jdk 1.8)
    3. Deployed SSPR (deployment was successful - tomcat started for once and I can see sspr in webapps along with sspr.war)

    Now when I start tomcat using ./catalina start, I get the below:

    Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
    At least one of these environment variable is needed to run this program


    If I set the JAVA_HOME and JRE_HOME environment variables, tomcat starts but I do not get anything on the browser, infact I do not get anything even if I type http://localhost:8080.
    Secondly, JAVA_HOME and JRE_HOME variables are also lost later and then I am back to the message, where tomcat won't start and it says "Neither the JAVA_HOME......."

    I would want this instance of tomcat to use a different java version 1.8 and let the older tomcat use the java it is using (1.7).
  • On 1/29/2018 11:04 AM, pranavjo wrote:
    >
    > So, this is what I did on another machine (where IDM/eDir is already
    > installed)
    > 1.Placed tomcat 8.5 (tomcat 7 that comes with novell is already there).
    > 2.Installed java (jdk 1.8)
    > 3. Deployed SSPR (deployment was successful - tomcat started for once
    > and I can see sspr in webapps along with sspr.war)
    >
    > Now when I start tomcat using ./catalina start, I get the below:
    >
    > -Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
    > At least one of these environment variable is needed to run this
    > program-
    >
    > If I set the JAVA_HOME and JRE_HOME environment variables, tomcat starts
    > but I do not get anything on the browser, infact I do not get anything
    > even if I type http://localhost:8080.
    > Secondly, JAVA_HOME and JRE_HOME variables are also lost later and then
    > I am back to the message, where tomcat won't start and it says "Neither
    > the JAVA_HOME......."
    >
    > I would want this instance of tomcat to use a different java version 1.8
    > and let the older tomcat use the java it is using (1.7).


    in the IDM delivered installs of SSPR and Tomcat, in the tomcat\bin
    there is a file setenv.sh (Linux) that sets these values. And when
    Tomcat runs, the start process script uses this script to set the
    variables needed to run Tomcat.

    So I imagine you could run each with different values so long as they
    are started sequentially.