JICS : FWK_Globalization

There's a table called FWK_Globalization that's mentioned in almost every JICSWiki entry, but I have no idea what it does. It's probably important.

JICS : LDIF files and ADAM

When a portlet is installed, we have to stick some data into ADAM so JICS knows that our portlet exists.

Related pages :

http://www.jicswiki.com/index.php?title=GeneratingLDIFFiles
http://www.jicswiki.com/index.php?title=InstallingPortlets

JICS Secured Portlets

We can create a portlet that inherits SecuredPortletBase, instead of PortletBase.  This lets us create security levels in our portlets that can be administered by the JICS site administrator using the Global Portlet Operations page (Site Manager > Site Settings > Global Portlet Operations > Edit).  By default, we can set "canAccess", which will allow the administrator to set which users can view the portlet.  We can optionally add other security levels, such as "Admin", or we could hide and show views for different departments.

Related Links :
http://www.jicswiki.com/index.php?title=CreatingAPortlet
http://www.jicswiki.com/index.php?title=Resync_Operations
http://www.jicswiki.com/index.php?title=Global_and_Portlet_Operations

JICS Portal Templates

Question : I saw a reference to portal templates someplace. I'm wondering if there's anything to it.

JICS Portal Inheritance

Question : We should be able to write one portal that inherits code from another portal. However, the existance of .ascx files make this problematic, because .ascx files don't play well with inheritance. Are there any examples of this being done?

JICS : ASCX pages

With web controls, you have an .ascx page that defines how things look, and a .dll file that contains the code for the page. The info below is gleaned from JICS Portlet Creation page

Create a different .ascx file for each view.

There are two required views. Default_View, and Main_View. The ascx files for these must be located in Default_View.ascx and Main_View.ascx.

All the .ascx files for the portlet go in their own directory on the server

Every portlet has it's own directory. That directory goes in [Type]\Portal\Portlets\CUS\[Portlet name]. For more info on this directory, see "Naming Conventions"

All the .dll files for all portlets go in one directory

That directory is \Portal\bin

Question : How does the system know where our portlet's .ascx files are located?

Question : Can we build a portlet that has all the web controls defined in the .dll, and doesn't have an .ascx page?

Question : It looks like there are add-ons, such as LMS and CRM, that have their own portal directories. Do LMS portlet dll's go in LMS\Portal\bin, or is there a master \Portal\bin where all the data goes?

JICS Naming Conventions

Naming standard page : JICS Wiki

Portlets should be named :

[Two character ERP type] + [Short description] + [Institution Name]

Tables should be named :

"CUS_" + [Portlet name] + [table description]

Assemblies should be named :

"Portlet." + [Portlet name]

Root directory for .ascx files should be :

"\Portlets\CUS\" + [User-defined Subdirectory (optional)] + [Portlet name]

Question : Why are they removing the word 'portlet' from directory, namespace, and class names, but leaving it there for assembly / dll names?