Fri 20 Jul 2012
Current snapshot builds of the GSF (as available on the GSF website) have “some issues” with the installation on 11gR1, mostly around permissions, that do not arise on 7.6. I’m working on addressing these and hope to have it sorted out in the next week or so.
Meanwhile, here are some step-by-step instructions that will take you through complete installation of the GSF on a virgin 11gR1 installation. They are aimed at a trained WC Sites administrator / developer.
If you have any questions or corrections, please let me know.
Core GSF Installation
- Download GSF kit from site
- Copy the GSF jar to war (webapps/cs/WEB-INF/lib)
- Copy the “gsf” folder to webapps/cs
- Start cs and deploy elements that ship with the GSF using CatalogMover
- Log in to the UI, choose Admin site and GSF application
- In the WEM ui, go to the WEM admin app
- Create a new site
- Add users and roles to site
- Add CS Admin, GSF, Contributor, and WEM admin app to the new site
- Add CS Admin, Contributor, and WEM admin apps to the GST site (also)
- Log out & log in (this might be done in one step)
- Select GST site and open the CS Admin app
- Using the “replacement tree”, select Sites > GST > Asset types, and disable all asset types. Repeat the process and ENABLE all asset types starting with GST*
- In the admin ui, select Sites > YOUR NEW SITE and enable asset types GST*, CSElement, Template, SiteEntry, Page, Page Attribute, Page definition, and AttrTypes
- Search for all attributes & share them with your new site! Repeat for definitions.
- In your site, create a new CSElement called exactly: “GST/Dispatcher”. It will be automatically populated. Delete the XML comment if there is one. Change the action from “…ActionController” to “com.fatwire.gst.foundation.controller.BaseController” (for now - let’s start simple)
- Create a new SiteEntry called “YOURSITE/Dispatcher” using the element you just created. Wrapper, uncached. (This is a workaround to the fact that the SiteEntry asset is created but is not accessible in your site)
Configuring the GSF Vanity URL support
This topic is a little more involved and is not necessary for initial development, so I’ll cover it in another post, later.
Creating a sample site in the GSF
- Create a new GSTAttribute called “body”, make it text.
- Create a new GSTDefinition called “MyArticle” containing the following:*h1titlte,*metatitle, *metadescription, linktext, body, *metakeyword
- Create a new Flex child under GST Attribute called YOURSITEContent and enable it for your site, edit the asset type so that it “can be child”
- Create a new template called “Microsite” for asset type YOURSITEContent and subtype “MyArticle”. Usage: Layout; type: JSP; code: from microsite.jsp file in the GSF kit; cached.
- Create a new pageDefinition called “Blank”
- Create a new named association under “Page” called “-”, Description “Contains”, Child Asset “Any”, Page Subtypes “Blank”. Exists, Multivalued. (this retrofits the unnamed association into the 11g page asset)
- Switch to contributor UI and create a new YOURSITEContent (definition MyArticle)
- Save it, then select a template (Microsite), then save it AGAIN
- Create a new Page called “MainNav”
- Create sub-pages under MainNav called “Home”, “About”, “Contact”
- Hook up your new MyArticle to the Home asset’s Contains slot.
- Create 2 new MyArticles and add them to the About and Contact Contains Slots.
- Once this is finished, your microsite template should render your site and create a full nab bar