1)  External Table Database update- The external_student_test table has a new column named discriminator and included in the primary key definition.  When deploying 2.1, the new column will be added regardless of the values of db_liquibase_external_apply_natural_keys.  The default value of 'discriminator' is '1'. The application does not care what values are set.  It is intended to be a completely opaque value used exclusively to distinguish between multiple completion of the same test on the same date.  The application will fail to start if duplicate data exists in the table.  In those cases, follow the steps below:

• Deploy and start up the 2.1 code with db_liquibase_external_apply_natural_keys=false. This will create the new column and fill in default values (1).
• Adjust or reload the external_student_test table with discriminator values to eliminate duplicate keys
• Restart the application with db_liquibase_external_apply_natural_keys=true. This will attempt to add a primary key to this table, including the discriminator column.

2)  Remove unused permissions with SQL

• delete from up_permission where activity in ('PERSON_TEST_READ','PERSON_TRANSCRIPT_READ');
• delete from up_permission_activity where activity_fname in ('PERSON_TEST_READ','PERSON_TRANSCRIPT_READ');

3)  Add new permissions for configurable Confidentiality Levels

• ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-1-0/SSP-1466 data-import

4)  Add new bulk reassign permission for the Caseload Reassignment tool

• ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-1-0/SSP-1762 data-import

5)  Add SSP adminsitrators to the uPortal administrators group

• ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/group_membership/Portal_Administrators.group-membership.xml data-import

6)  Correct the DATA_ENGLISH_SECOND_LANGAGE permission

• update up_permission set activity = 'DATA_ENGLISH_SECOND_LANGUAGE' where activity = 'DATA_ENGLISH_SECOND_LANGAGE'
• update up_permission_activity set activity_fname = 'DATA_ENGLISH_SECOND_LANGUAGE', activity_name = 'DATA_ENGLISH_SECOND_LANGUAGE' where activity_fname = 'DATA_ENGLISH_SECOND_LANGAGE'

7)  SSP-1668 represent a fix for case-insensitive user searches in uPortal.  The personDirectoryContext.xml has been modified in upstream versions including 2.1.0.  Any existing implementation should review the changes and appropriately configure.  The details of the change are described in the uPortal pull request.

8)  A new config option in portal.properties was added to exclude certain uP-local attributes from automatic wildcarding. The default exclusion list is SSP_ROLES, which is desired forSSP because searches on that attribute almost always include the list of current coaches in which case exact matches only are desired. See https://github.com/Jasig/uPortal/commit/d530d7abc94a20c051c43a010708f4979f233456 for where that config lives (portal.properties). The commit includes detailed comments in that file.

Deployers shouldn't need to do anything as a result of the new exclusion list config option unless there are scenarios where search on SSP_ROLES with wildcards is desired.  In that case, the following steps should be taken.

1. Add those wildcards explicitly to their search terms (which will not work if also querying against multi-valued LDAP attributes), or
2. Remove SSP_ROLES from the exclusion list (which will potentially results in non-exact uP-local matches)

Also, keep in mind that per its traditional behavior, uP searches on non-username attributes are automatically wildcarded by default. In non-uP local PD DAOs you need to explicitly enable that behavior.  The notes in #7 referred to above explain how to do this.Per SSP-1838 and SSP-1981, a new message template for the MAP Templates has been introduced to print templates.  This will not affect any existing message templates.  The message template definition exists in the Configuration Guide.

2)  Per SSP-1894, the Full Plan Message Template and Matrix Plan Message Templates have changed to consistently display contact information for both the owner and assigned coach.  Since implementers may have modified the message templates, the upgrade will ONLY update the message template definition IF no changes from the default have been made.  IF changes to the message template(s) have been made, the changes can be manually made in the SSP Admin Configuration.  The code snippets below details the portions of the templates that have changed:

Old

<p style="padding-left:20px;font-size:small;margin-top:30px;">
	<strong>If I have questions or concerns about my plan I will contact:</strong>
	</p>
	<p style="padding-left:20px;padding-left:20px;font-size:small">
		<strong>
	#if("$!contactName" != "") $!contactTitle $contactName #else $coachFullName #end</br>
	#if("$!contactPhone" != "") $contactPhone #else $coachPhone2 #end</br>
	#if("$!contactEmail" != "") $contactEmail #else $coachEmail #end
	</strong>
	</p>
------------------------------------------------------------------------------------------------
New

<p style="padding-left:20px;font-size:small;margin-top:30px;">
	<strong>If I have questions or concerns about my plan I will contact:</strong>
	</p>
	<strong>
	<p style="padding-left:20px">
	$!contactName</br>
	$!contactTitle</br>
	$!contactPhone</br>
	$!contactEmail
	</p>
		
	<p style="padding-left:20px">
	$!ownerFullName</br>
	$!ownerPhone</br>
	$!ownerEmail
	</p>
	</strong>
	</p>

Old

<b>If I have questions or concerns about my plan I will contact:
	</p>
	<p style="padding-left:20px">
	$!coachFullName</br>
	$!coachPhone2</br>
	$!coachEmail
	</p>
------------------------------------------------------------------------------------------------
New 

<b>If I have questions or concerns about my plan I will contact:
	</p>
	<p style="padding-left:20px">
	$!contactName</br>
	$!contactTitle</br>
	$!contactPhone</br>
	$!contactEmail
	</p>
		
	<p style="padding-left:20px">
	$!ownerFullName</br>
	$!ownerPhone</br>
	$!ownerEmail
	</p>

3)  Per SSP-1894, in addition to the default message template changes for MAP, the Velocity context variables $coachPhone1, $coachPhone2, $coachEmail, $coachFullname have been replaced with $ownerPhone, $ownerFullname, and $ownerEmail. The single phone number points to the owner's 'work_phone' (as opposed to home and cell phone with the previous variables). $student , the student 'person' object has been also added to this messages' scope.  The new variables should replace the existing variables in customized message templates

4)  Per SSP-1881, changes to the uPortal tables to harmonize the column size for user name were made.  The database changes will be made by the upgrade process UNLESS uPortal and SSP DO NOT share the same schema.  In the case where two different schemas are used, the SQL for updating the tabes must be run manually.

alter table up_person_dir alter column user_name type varchar(50);
alter table up_user alter column user_name type varchar(50);
alter table up_sso_ticket alter column user_name type varchar(50);
alter table up_raw_events alter column user_name type varchar(50);

alter table up_person_dir alter column user_name  nvarchar(50);
alter table up_user alter column user_name  nvarchar(50);
alter table up_sso_ticket alter column user_name  nvarchar(50);
alter table up_raw_events alter column user_name type nvarchar(50);

5)  Per SSP-1888, the uPortal build-time configuration options previously defined in <env>.properties (commonly local.properties) have been moved to a new file that is available during run-time.  Most importantly, configuration changes can be executed by restarting the application with no requirement to build.  This accounts for the most common build options.  The new file name and location are <SSP_CONFIGDIR>/ssp-platform-config.properties.  To ensure the latest configuration options are included in the local file, review the latest ssp-platform-config.properties at ./uportal-war/src/main/resources/properties/ssp-platform-config.default.properties. 

For future uPortal builds involving 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 initdb