In this recipe, we will the existing default portal site, referred to as classic, and modify the configuration files to rename the portal before importing it into GateIn.
The following are required for this recipe:
To replicate the classic portal:
> ssh -p 2000 root@localhost
> mgmt connect
> export --file /tmp/portal.zip --filter site-name:classic /mop
portal.zip
, which was created above.portal/classic
folder to portal/testing
.portal.xml
by changing <portal-name>
to testing
, <label>
to Testing
and <description>
to GateIn Testing
.navigation.xml
by replacing all references to the classic
portal name with testing
, including the <page-reference>
nodes and the labels of samplePage
and groupnavigation
changed to Sample Page
and Group Navigation
respectively.> import --file /tmp/portal.zip /mop
http://localhost:8080/portal/testing
and the new portal will appear as shown in the following screenshot:Step 6 exports the entire classic
portal site from GateIn, including portal configuration, pages, and navigation nodes.
The output from Step 6 can also be used as a way to migrate portal page content and structure from one environment to another. With the CLI import command, you can replace the environment's content with the newly exported ZIP file. Note that there are many other facets to a full migration, such as portlet applications and any portal customization.
Steps 8, 9, and 10 modify the configuration that was exported from the classic
portal, and rename it to testing
. Renaming the portal will create a new portal in GateIn as part of the import process, accomplished in Step 11.
18.227.52.208