Skip to main content

Posts

Showing posts from June, 2013

Web Center: using a custom security provider other than LDAP [custom identity store]

So far everything looks like it will work I am just using the default auth provider and UCM is picking up my groups on login so now to integrate with Web center and use my custom auth provider. Custom authentication provider is done and I can log in to my content server and application and everything is working. The snag is not of the webcenter custom profile pictures and webcenter goodies are working (it uses the JpsContextFactory etc and that ignores my provider and looks up the default weblogic provider and tries to use that). I have replaced the identity store with a custom database implementation and everything seems to work [after a LOT of debugging]. Ok so step 1) The custom authentication provider - tons od documentation on how to do this eg:  http://docs.oracle.com/cd/E12890_01/ales/docs32/dvspisec/progrmng.html ,  http://docs.oracle.com/cd/E13222_01/wls/docs81/dvspisec/atn.html  so I am not going to rehash this if you want I can post some code but it shoul...

Adding a custom attribute WebCenter menu...

Find the schema section in your menu xml --> ie default-navigation-model.xml Add a descriptor:     <descriptor shortLabelKey="TITLE.SHORT_PROMPT_KEY" multivalue="false"                 attributeId="NewAtrr" labelKey="TITLE.PROMPT_KEY"                 endUserVisible="true" searchable="true"                 xmlns="http://xmlns.oracle.com/adf/rcs/catalog"/> Note: you can change the  shortLabelKey and labelKey by adding a resourceBundle="..." but that is another post.... Looks a bit like this: <schema resourceBundle="oracle.adf.rc.attribute.nls.AttributeBundle"           xmlns="http://xmlns.oracle.com/adf/rcs/catalog">     <descriptor shortLabelKey="TITLE.SHORT_PROMPT_KEY" multivalue="false"                 attributeId="Title" labelKey="TITLE.PROM...

Automated remote deployment of Webcenter ear to our development enviroment

All the usual undeploy / stop start code worked remotely but unfortunately the deploy was not going as planned - I wanted to set the MDS info on deployment so it was time for a new plan. So this time on our build server would call WLST to deploy our web center app on the development weblogic enviroment. Wlst commands I used: Connect   connect('weblogic','bobsentme', ''t3://remote.wl:7001') Stop   shutdown('ManagedServer1', force='true') Start   start(start('WC_Cluster', 'Cluster', 't3://remote.wl:7001')); Deploy archive = getMDSArchiveConfig(fromLocation='/tmp/pathto.ear') archive.setAppMetadataRepository(repository='mds-CustomDS', partition='dev_partition', type='DB', jndi='jdbc/mds/CustomDS')"); archive.save() deploy(appName='OurAppName', path='/tmp/pathto.ear', targets='WC_Cluster', stageMode='stage',   upload=...