Prerequisite setup

Just as with portal personalization, we recommend that you make customizations in a separate environment for portal development. For cloud customers, this is the TRN environment. For on-premises customers, this environment should have a separate machine with the IPF Control Service, IIS, and a different IPF Control Database instance. When portal customizations are finished and tested, you can close the content for development, export it from the development environment, and import it into the production environment. The content can then be activated for use in the production portal(s). This is described in the portal administration guide.

To customize portal content, you must set up developer users and enable the portal for development. These are the same requirements as for personalizing the portal. Steps are provided in the portal administration guide.