WebSphere Portal SSO Config

Another short.

When configuring a portal for SSO with a custom login servlet and using the Portal session management JSP's it took some digging to track down what was required to disable the login Portlet.




In order to enable screens for login it is necessary to:
set authentication.screen.login = true

Resources > Resource environment providers > WP AuthenticationService > Custom properties

authentication.screen.login
Default: false
Custom: true
java.lang.String

Read more about Portal configuration services, and settings in Infocenter:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wps/srvcfgref.html

Also, remove the Login portlet from the Welcome page.
When using screens instead of the Selfcare or Login portlet,
add the puma.controllerHTML = com.ibm.wps.puma.PumaControllerHTML

property in the IBM WebSphere Conole:

Resources > Resource environment providers > WP PumaService > Custom properties

puma.controllerHTML = com.ibm.wps.puma.PumaControllerHTML

How to export/import WebSphere Portal 6 WCM and PDM data

This is a short post on how to export/import WebSphere Portal 6 WCM and PDM data using the IBM migration tools.
I haven't had only positive results in using the tools, especially on win32 where java memory constraints with contiguous memory is a big limitation.

# Confirm that the following properties in the init section are set as specified, modifying the properties if necessary:

Note: All samples containing <\property> e.g, require removal of backslash "\".

# 1. On source server, export PDM libraries

cd d:\IBM\WebSphere\PortalServer\migration
call ..\..\profiles\wp_profile\bin\setupCMDLine.bat
# Sample: <\path to samples>/SAMPLE_pdm60_s2p_conf.xml
ExportDir/ImportDir
SourceServerPort/TargetServerPort
ExportUserId/ExportPassword

<\property name="DocLib" value="Document Manager"/>
<\property name="DocLibProperty" value="icm:title"/>


# Edit: d:\IBM\WebSphere\PortalServer\jcr\migration\conf\pdm60_s2p_conf.xml
WPmigrate.bat staging-to-production-pdm60-export

# 2. On source server, export WCM libraries

cd d:\IBM\WebSphere\PortalServer\config
call ..\..\profiles\wp_profile\bin\setupCMDLine.bat
# Sample: <\path to samples>/SAMPLE_wcm60_conf.xml
MigDirSource/MigDirTarget


** I had two Weblib's, so there's a requirement for two separate export/import-tasks.

<\property name="WebLib" value="Acme Library"/>
<\property name="WebLib" value="Acme Administration"/>

<\property name="WebLibProperty" value="icm:title"/>

# Edit: d:\IBM\WebSphere\PortalServer\jcr\migration\conf\wcm60_conf.xml
WPSconfig.bat export-wcm-data


# 3. On target server, import PDM libraries

cd d:\IBM\WebSphere\PortalServer\migration
call ..\..\profiles\wp_profile\bin\setupCMDLine.bat
# Sample: <\path to samples>/SAMPLE_pdm60_s2p_conf.xml
# Edit: d:\IBM\WebSphere\PortalServer\jcr\migration\conf\pdm60_s2p_conf.xml
WPmigrate.bat staging-to-production-pdm60-import

# 4. On target server, import WCM libraries

cd d:\IBM\WebSphere\PortalServer\config
call ..\..\profiles\wp_profile\bin\setupCMDLine.
# Sample: <\path to samples>/SAMPLE_wcm60_conf.xml
# Edit: d:\IBM\WebSphere\PortalServer\jcr\migration\conf\wcm60_conf.xml
WPSconfig.bat import-wcm-data


## Notice: errors...
com.ibm.wps.odc.convert.ConvertorException: Stellent Conversion Error: file is corrupt

Web Content Management nominates objects to be text searchable. To index each object,
JCR hands over the object to ODC code if the elementData value of an object is flagged as "textSearchable."
By default, we set textSearchable flag at a global level.
This global settings means that certain objects that should not be textSearchable are.
These objects do not cause problems on the system but do throw warning exceptions.