Versions Compared

Old Version 3

changes.mady.by.user Jason Elwood

Saved on

compared with

New Version Current

changes.mady.by.user Daniel McCallum

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

For all existing installations of 2.0.X and 2.1.X, important upgrade instructions exist in the previous 2.1,  2.2, 2.3 and 2.4 Release notes. 

  • To upgrade from 2.0.X follow the upgrade instructions for 2.1,  2.2,  2.3 and 2.4 Release Notes before deploying the 2.4 code
  • To upgrade from 2.1.X follow the upgrade instructions for the 2.2,  2.3 and 2.4   Release Notes before deploying the 2.4 code
  • To upgrade from 2.2.X follow the upgrade instructions for the  2.3 and 2.4  Release Notes before deploying the 2.4 code
  • To upgrade from 2.3 follow the 2.4 Release Notes before deploying the 2.4.1 code
  • New installations of 2.4.1 are not required to make any additional change

If you are running a SSP version prior to 1.1.1, you are strongly encouraged to upgrade or otherwise apply the reporting subsystem security patches described by SSP-701.

If you are running SSP version 2.0.0 or 2.0.0-b3, you are strongly encouraged to upgrade to 2.0.1 or 2.1.0 or 2.2.0 or later or otherwise apply the Confidentiality Level-related patches for the Student Documents tool as described by SSP-1917.

All implementers of this release should consider installing the patches listed in the commit section of the SSP-2721 issue details.

Also please take a few minutes to review additional security-related announcements detailed at the top of the SSP space here in Confluence.

...

Code Block
*** When running a database initialization ant target (initportal, initdb), you need to specify SSP_CONFIGDIR if it isn't already specified as an env var. 

E.g on *nix.... $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean <target> 

Most Common Commands

- BuildRe/Initialize entirethe uPortal (incl. all wars), deploy entire uPortal, ant SSP-Platform database, then run the equivalent of deploy-ear. Destructive! -Appropriate Buildfor the full site and database, ant initportal (Warning- this will reset the entire uPortal database)


Other deployment optionsfirst-time deployments.

  $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean initportal

- Build and deploy entire SSP-Platform portal, including SSP:

  $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean deploy-ear


Other commonly used ant targets:

testdb: Tests the database settings and connectivity

initdb: Drop uPortalSSP-Platform tables in the db & recreate them with configured seed data (src/main/data, not including the "quickstart" folder).

deploy-war: Build & deploy _just the uPortalSSP-Platform war_ (i.e. not SSP or other portlets, etc.).

deployPortletApp: Deploy one (already-built) portlet war file to Tomcat (example ant deploPortletApp -DportletApp=..\/SSP-Open-Source-Project/target/ssp.war)
Info
titleNOTE
This command will download the SSP .war file and bundle it into the output of the SSP-Platform build
)

 

 

  • Additional step for Microsoft SQL Server to update column types

...

6. Production Deployment Tips

  • Warning
    titleDelete Demo Users

    If you are deploying to upgrading a production environment, you should delete or change the passwords for the uPortal users created for demonstration purposes, including the admin user. This can be done through the user interface: Manage Users ->  Find an Existing User -> [Enter user ID from list below] -> [Click result] -> > Delete or  or Edit, then change password. Demo users:

    admin

    • advisor0
    • ken
    • student0
    • student1

    This is only necessary for upgrades. A fresh 2.4.1 install will not create these users.

    A fresh install should also either change the admin user's password or add some other user to the Portal Administrators group and delete the admin user.

If anything in it is incorrect or unclear, please leave a comment below.

...