Enportal/old/upgrading to enportal 5 - Revision history

imported>Nick.chang: /* Post-upgrade work */

2014-07-30T19:41:16Z

Post-upgrade work

← Older revision		Revision as of 19:41, 30 July 2014
Line 57:		Line 57:
	This step tweaks the configuration of enPortal 5.x to properly recognize the content that was loaded in the steps above.		This step tweaks the configuration of enPortal 5.x to properly recognize the content that was loaded in the steps above.

	* Use saved personalization.xml as a guide to identify the content to be provisioned and the assignment to the roles.
	* Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)
	* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)		* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)
			* Run LDAP Sync to sync the roles with LDAP if the roles are managed by an LDAP server.
			* Use saved personalization.xml as a guide to identify the content to be provisioned and its assignment to the roles.
			* Migrate the old content location to a centralized location in /deployment/Menu folder. Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)
	* Manually assign appropriate content (Folders and Channels) back to Roles, as to match assignments in the previous system.		* Manually assign appropriate content (Folders and Channels) back to Roles, as to match assignments in the previous system.
	* Run regression test plan to validate changes		* Run regression test plan to validate changes

imported>Nick.chang: /* Post-upgrade work */

2014-07-30T19:36:06Z

Post-upgrade work

← Older revision		Revision as of 19:36, 30 July 2014
Line 57:		Line 57:
	This step tweaks the configuration of enPortal 5.x to properly recognize the content that was loaded in the steps above.		This step tweaks the configuration of enPortal 5.x to properly recognize the content that was loaded in the steps above.

			* Use saved personalization.xml as a guide to identify the content to be provisioned and the assignment to the roles.
	* Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)		* Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)
	* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)		* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)
	* Manually assign appropriate Folders and Channels back to Roles, as to match assignments in the previous system		* Manually assign appropriate content (Folders and Channels) back to Roles, as to match assignments in the previous system.
	* Run regression test plan to validate changes		* Run regression test plan to validate changes

imported>Nick.chang: /* XML Import/Export */

2014-07-30T19:34:06Z

XML Import/Export

← Older revision		Revision as of 19:34, 30 July 2014
Line 49:		Line 49:
	** dirMetaInfo.xml		** dirMetaInfo.xml
	** styles.xml		** styles.xml
	* ~~Remove old LAF dependencies by updating the~~ personalization.xml file~~. Removing any assignments such~~ as the ~~following~~ in ~~personalization.xml:~~		** personalization.xml* (save this file as reference for the role content assignment in subsequent steps)
	** <LAFConfig preferredLAF="/system/LAFs/old laf"> </LAFConfig>
	* Move the sanitized "backup" directory to the 5.x directory or server		* Move the sanitized "backup" directory to the 5.x directory or server
	* Create a custom load file (load<customname>.txt) and use the XMLImport channel (under Advanced tab) to load the sanitized enPortal 4.x backup into enPortal 5.x		* Create a custom load file (load<customname>.txt) and use the XMLImport channel (under Advanced tab) to load the sanitized enPortal 4.x backup into enPortal 5.x


	== Post-upgrade work ==		== Post-upgrade work ==

imported>Jason.nicholls at 17:28, 17 July 2014

2014-07-17T17:28:05Z

← Older revision		Revision as of 17:28, 17 July 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:Upgrading to enPortal 5}}		{{DISPLAYTITLE:Upgrading to enPortal 5}}
			[[Category:enPortal old]]

	enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5.4/overview/whats_new_enportal\|enPortal 5.4 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.		enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5.4/overview/whats_new_enportal\|enPortal 5.4 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.

imported>Jason.nicholls: moved Upgrading To enPortal 5 to enportal/old/upgrading to enportal 5

2014-07-17T17:27:41Z

moved Upgrading To enPortal 5 to enportal/old/upgrading to enportal 5

← Older revision	Revision as of 17:27, 17 July 2014
(No difference)

imported>Jason.nicholls at 15:56, 19 December 2013

2013-12-19T15:56:05Z

← Older revision		Revision as of 15:56, 19 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Upgrading to enPortal 5}}		{{DISPLAYTITLE:Upgrading to enPortal 5}}

	enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5/overview/whats_new_enportal\|enPortal 5.4 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.		enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5.4/overview/whats_new_enportal\|enPortal 5.4 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.

	The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.		The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.
Line 24:		Line 24:

	After completing the Pre-Upgrade Work described above, install enPortal 5 in the new directory or server. <br>		After completing the Pre-Upgrade Work described above, install enPortal 5 in the new directory or server. <br>
	To do so, follow the [[enportal/5/admin/enPortal_installation/installation\|enPortal 5.x installation]] instructions.		To do so, follow the [[enportal/5.4/admin/enPortal_installation/installation\|enPortal 5.x installation]] instructions.

imported>David.moore: /* Post-upgrade work */

2013-12-06T14:57:51Z

Post-upgrade work

← Older revision		Revision as of 14:57, 6 December 2013
Line 60:		Line 60:
	* Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)		* Share content folders to deployment area by right-click on folder in directory and sharing to deployment/Menu (this makes it available for provisioning to Roles under the Content tab)
	* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)		* Create new LAF in 5.x (re-using images from 4.x LAF where applicable)
	* Manually assign appropriate ~~Views~~ back to Roles, as to match assignments in the previous system		* Manually assign appropriate Folders and Channels back to Roles, as to match assignments in the previous system
	* Run regression test plan to validate changes		* Run regression test plan to validate changes

imported>David.moore at 14:46, 6 December 2013

2013-12-06T14:46:39Z

← Older revision		Revision as of 14:46, 6 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Upgrading to enPortal 5}}		{{DISPLAYTITLE:Upgrading to enPortal 5}}

	enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5/overview/whats_new_enportal\|enPortal 5.0 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.		enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5/overview/whats_new_enportal\|enPortal 5.4 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.

	The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.		The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.

imported>Mylene.stolpe at 20:27, 26 November 2013

2013-11-26T20:27:03Z

← Older revision		Revision as of 20:27, 26 November 2013
Line 24:		Line 24:

	After completing the Pre-Upgrade Work described above, install enPortal 5 in the new directory or server. <br>		After completing the Pre-Upgrade Work described above, install enPortal 5 in the new directory or server. <br>
	To do so, follow the [[enportal/5/installation\|enPortal 5.x installation]] instructions.		To do so, follow the [[enportal/5/admin/enPortal_installation/installation\|enPortal 5.x installation]] instructions.

imported>Mylene.stolpe at 20:17, 26 November 2013

2013-11-26T20:17:54Z

← Older revision		Revision as of 20:17, 26 November 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Upgrading to enPortal 5}}		{{DISPLAYTITLE:Upgrading to enPortal 5}}

	enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5/~~whats_new_from_legacy_enportal~~\|enPortal 5.0 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.		enPortal 5 contains many significant changes from previous versions of enPortal. The major changes are detailed in [[enportal/5/overview/whats_new_enportal\|enPortal 5.0 New Features]]. Due to the significant changes between enPortal 4.x and enPortal 5.x, special steps are needed to upgrade an enPortal 4.x system to enPortal 5.x.

	The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.		The upgrade process primarily manages the specific transition of the provisioning of content. In enPortal 4.x, the administrator could provision (assign) content directly to Roles, Users, or Domains. In enPortal 5.x, all of the content must be provisioned by Role in order for it to work properly in the UI. If you had previously provisioned content by Role, then it should not be difficult to transition this to the new system. If not, then you may need to create new Roles for any Domains and Users that had content provisioned to them directly.