Use composite applications in a migrated virtual portal
Before using composite applications in a migrated v6.0.1.x virtual portal, run an additional configuration task to create root folders for templates and applications, and then import the composite application templates that you want to work with.
- Change to the WP_PROFILE/ConfigEngine and then run the command below:
- Windows™: ConfigEngine.bat upgrade-virtual-portal-for-ai -DWasUserid=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo -DVirtualPortalContext=vp_context
- UNIX™: ./ConfigEngine.sh upgrade-virtual-portal-for-ai -DWasUserid=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo -DVirtualPortalContext=vp_context
- i: ConfigEngine.sh upgrade-virtual-portal-for-ai -DWasUserid=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo -DVirtualPortalContext=vp_context
where VirtualPortalContext or VirtualPortalHost identifies the virtual portal context.
For example, executing the following command creates root folders for templates and applications in virtual portal vp1:
/ConfigEngine.sh upgrade-virtual-portal-for-ai -DVirtualPortalContext=vp1
- Use the Template Library to import the composite application templates that you want to work with in the virtual portal.
Parent
Migrate composite applications
Previous
Running migration tasks for composite applications
Related tasks
Use the Application Template Library