Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Introduction

uPortal now has an export/import system using xml files generated by Cernunnos export scripts.  Basically, you will run an export command on your existing portal project to generate a number of xml data files.  You then run import in your uPortal3 project to import the data from these xml files into your uPortal3 database.  Take a look at the Cernunnos overview to get a better understanding of this process.  After that, move on to reading about Exporting and Importing.

Default Database

The default database is populated by the db-import task in build.xml. This task is called by ant initdb, which in turn is called by ant initportal.  The db-import task actually uses crn-import to create the database:

         <antcall target="crn-import">
            <param name="dir" value="${basedir}/uportal-impl/src/main/resources/properties/db/entities" />
        </antcall>

As you can see, it simply calls crn-import on the entities directory.  Take a look at this directory to see the xml format for groups, layouts, channels, etc.

 Your Default Database

I highly recommend setting up an entities directory for your team.  This makes it easy for anyone working on your portal to populate their development database with the groups, channels, permissions, fragment-layouts, etc that your portal uses.  After you've completed your export copy your export folder under: uportal-impl/src/main/resources/properties/db

In my case, I called the folder calpoly_entities

The contents should look something like this:

channel:
channel files...

channel-type:
Applet.channel-type
Bookmarks_Portlet.channel-type
Image.channel-type
Inline_Frame.channel-type
Portlet.channel-type
RSS.channel-type
SQL.channel-type
Version.channel-type
Web_Proxy.channel-type
XML_SSL.channel-type
XML_XSLT.channel-type

entity-type:
java.lang.Object.entity-type
org.jasig.portal.ChannelDefinition.entity-type
org.jasig.portal.groups.IEntity.entity-type
org.jasig.portal.groups.IEntityGroup.entity-type
org.jasig.portal.security.IPermissionSet.entity-type
org.jasig.portal.security.IPerson.entity-type
org.jasig.portal.services.entityproperties.EntityProperties.entity-type

fragment-layout:
admissions-lo.fragment-layout
advising-lo.fragment-layout
asi-lo.fragment-layout
campus-nec-lo.fragment-layout
housing-lo.fragment-layout
library-lo.fragment-layout
main-lo.fragment-layout
money-lo.fragment-layout
orientation-lo.fragment-layout
personal-lo.fragment-layout
reg-enroll-lo.fragment-layout
tech-lo.fragment-layout
whats-lo.fragment-layout

fragment-users:
admissions-lo.user
advising-lo.user
asi-lo.user
campus-nec-lo.user
housing-lo.user
library-lo.user
main-lo.user
money-lo.user
orientation-lo.user
personal-lo.user
reg-enroll-lo.user
tech-lo.user
whats-lo.user

group_membership:
group membership files...

layout:
defaultTemplateUser.layout
fragmentTemplate.layout
guest.layout
system.layout
other users...

permission:
permission files...

structure:
DLM_Tabs_and_columns-1.structure

theme:
DLM_XHTML-1.theme

user:
defaultTemplateUser.template-user
fragmentTemplate.user
guest.user
system.user

  • No labels