Checklist: Deploy Enterprise Portal changes to a different server
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
The following checklist can help you deploy changes from one Enterprise Portal server to a different server. Changes can include updates to Enterprise Portal objects in the Application Object Tree (AOT), updates to SharePoint Web Parts, or the transfer of a whole Enterprise Portal site to a different server. The checklist includes links to procedure topics that contain the step-by-step instructions to complete a task.
Checklist for deploying Enterprise Portal changes to a different server
Task |
For more information, see… |
|---|---|
If you changed Enterprise Portal pages, you must import a copy of the page definition from SharePoint into the Application Object Tree (AOT). From the AOT, the page can be packaged for distribution to other Enterprise Portal installations. |
|
Export the changes from the AOT, so that they can be distributed to other Enterprise Portal installations. |
|
Import the changes to the AOT on the new server. |
|
Right-click the AOT project and then click Deploy to EP. Or, use the AxUpdatePortal.exe utility to update the web-related items from the AOT. |
Important
If you made significant changes to a site and you want to deploy the whole site to a new server, see Move an Enterprise Portal deployment to a different server.