Brio. Portal Implementation at the IMF Nathan Stratton Treadway Ray Ontko & Co. nathanst@ontko. com Brio Mid-Atlantic Users Group Wednesday, May 9, 2001
Session Overview ) ) ) ) Project Environment Portal Requirements Architecture Overview Security Interface Report Load Manager SPECT Utility Pitfalls and Tips Resources
Project Environment ) People. Soft 6 Financials ) List of projects defined in a People. Soft security tree Tree " " includes Division: TGSIA, TGSIB, etc. Sections: TGSIAS 1, TGSIAS 2, etc. Units: TGSIAS 1 U 1, TGSIAS 1 U 2 Projects: B 0001, B 0002, etc. ) Custom table and panel used to grant permissions from "Network Id" to tree nodes
Portal Requirements ) Users need to see reports based on their permissions ) Minimize manual maintenance of Portal security info ) [No external authentication source available (LDAP, etc. )] ) Minimize need for in-house Java skills
Architecture Overview, I ) Security Interface -- SQR from People. Soft to Portal using "Brio. Portal Security" (BPS) system ) Report Load Manager -- SQR Loads report files into proper Category (from Unix directories) ) SPECT -- Java (ONE/API) called by the Security Interface and the Load Manager to perform actual changes in Portal
Architecture Overview, II ) SQR used to generate various reports on People. Soft budget data most reports run nightly in Maestro at each level of the Project tree hierarchy and loaded into proper category several reports also loaded into Portal to allow "ad hoc" executions based on current Portal user ) A few related interfaces generate log files, which are loaded directly into hard-coded Portal categories
Architecture Overview, III ) Current statistics (approx): 100 users 50 groups 175 categories " " 50 45 based on Project nodes, plus three additional archive categories for each node remaining categories are for interface logs, etc. SQRs' output being loaded into Portal (both reports and interface logs)
Security Interface ) ) runs nightly from Maestro/cron written in SQR (3 parts) writes a SPECT file, then calls SPECT uses several local Oracle tables to keep track of changes made in "source" systems (staging tables) ) modular structure allows security information to be obtained from several sources People. Soft Projects tree other trees, "Group Security" table/panel
Report Load Manager ) also written in SQR ) also generates file and calls SPECT ) uses report file name to look up report properties and calculate the destination category (staging tables / business rules in code) eg. imfpc 212_TGSI. pdf or imfpc 212_TGSIAS 1. pdf ) invoked with a directory path and filename mask, loads all reports that match
SPECT ) Java ONE/API program ) reads a text control file and performs specified actions to Portal repository ) released under the GPL ) download from http: //www. ontko. com/portal/spect (new version for Portal v 7 is currently in development)
Sample SPECT control file ) ) ) create user Test. User password=welcome description="Test User" ; update user Test. User email="testuser@somewhere. com"; update category "/Demo/Private" group=Employee permissions=700; ) delete file "/Demo/Private/Demo. doc";
Pitfalls and Tips, I Choosing Category Structure, I ) Categories sort in alphabetical order on Portal display choose category names carefully -- we started ours with the tree node name categories such as "IMFIAS 1 Section Title" sort BEFORE "IMFI Dept Title" in the category listing Project categories had to be treated specially, since project names don't sort correctly (Bxxxx instead of TGSxxxxx)
Pitfalls and Tips, II Choosing Category Structure, II ) Most users have access to only a few tree nodes low in the hierachy, so we flattened the structure inside of Portal (Flattened) ) TGSIAS 1 U 2 ) TGSIAS 2 (Unflattened) )TGSIA TGSIAS 1 U 1 "TGSIAS 1 U 2 " TGSIAS 2
Pitfalls and Tips, III Choosing Category Structure, III ) Consider archiving needs we originally just planned to save a large number of versions on each report object - too clumsy instead, we now have Weekly, Monthly, and Yearly archive subcategories " each report object has a maximum of only 8 -13 versions
Pitfalls and Tips, IV ) Choose output type(s) desired We concentrate on PDF since users need to print rather than browse on-line Dynamic jobs are set to "Run in Background" so HTML isn't automatically displayed to the user ) Portal patches SPECT "pushes the envelope" a bit on the ONE/API
Pitfalls and Tips, V ) Watch out for SQR output bugs various versions of SQR have limits on, and buggy generation of, PDF output many versions of SQR 4. 3. x and 5. x crash with "-burst: p. NN" option (for generating HTML output) SQRP included with Portal v 6 has problems with GIF files in PDF reports so, test each kind of output you need -you may need to use two versions of SQR simultaneously
Resources ) rm-users mailing list: http: //www. sqrug. com/rm-users ) Brio Tech Support FAQ: http: //briofaq. brio. com/scripts/faq. exe/ ) SQRUG Links page and Library : http: //www. sqrug. com
Скачать презентацию Brio Portal Implementation at the IMF Nathan Stratton
c1b6b2e78ac64249bec9b89216c0b862.ppt