Member Fixer with Syndication
kswarnam 270003T1EP Visits (5490)
Managed Pages is One of the new Features of WebSphere Portal 8 . Portal pages are basically treated like content and you will be able to syndicate a managed page from one environment to another . This helps the Business users to manage the full site creation process without the bottleneck of IT having to create the Portal page. This also mean that you do not have to manually export and import the portal pages from one environment to another using XMLAccess .With Portal 8 you can schedule the member fixer to be run automatically after each syndication .As portal page are stored as content in Portal site this means the member fixer will be run after each syndication and the portal page will be ready to use right away without IT help . I wanted to try out the scenario . I actually syndicated two pages 1.) with out configuring member fixer to run after each syndication 2.) run member fixer after each syndication .
1.) with out configuring member fixer to run after each syndication
I created a portal page under Home -> Welcome -> TestSyndication with default page permission . This is how it looked in the Portal site Library. Now i updated the subscriber in my delivery server to pick up this change . For this to work the syndicator - subscriber onfiguration should have be established .
In the delivery system once the syndication was completed this is how my portal site looked like
If you take a look at the author in the above screen shot the user Portaladmin does not exist in the destination system and is displayed as full dn .which can be updated to correct user dn using member fixer. Now i enabled the member fixer to run after each syndication and i create a new user sybdicationuser and testsyndication group in the source system and assigned the user and the group to a newly created Portal page TestSyndication2 . In the destination server i mapped the member fixer module for the syndicationuser to be replace with eexec and the testsyndication group with contentauthors.
This is how it looked in the source system
This saves a lot of manual work when syndicating portal pages from one lower environment to higher environment configured to different user repositories and helps faster time to market.