Bulk authorizing Oracle Unified Directory (OUD) users by adding them to OUD groups from the Linux/Unix Command Line

When using Oracle Unified Directory (OUD) as an identity store, it is in some occasions needed to add OUD users to OUD groups by hand. When you have to grant privileges to one user, this is easily done through the Oracle Directory Services Manager (ODSM) interface. However doing so for more then one user and more then one group, this might easily turn into a dreadful job. Luckily there are some command line utilities which can do that for you. In this blog I’ll guide you to the process on how I have done that with a given list of user names (e.g. Steven King, Neena Kochhar etc) and a gives list of groups (e.g. cn=Marketing,cn=Groups,dc=oracle,dc=org etc).

ADF 12c: Adaptive applications through reusable bindings using 12c Dynamic components, runtime switching from ADF BC to a POJO data control v.v.

The UK Oracle User group (UKOUG) held their Tech13, technology conference 2013, in Manchester 2 weeks ago. Duncan Mills held an interesting presentation on “Adaptive Applications”. He explained how to create fully reusable applications. Applications that can be used for different datasources and database tables. Just select a data model on runtime, and the application can show a page with a table. This can be done, eventhough using the ADFm Binding layer for all interactions by making it dynamic. With the dynamic binding layer is easy to reuse the same application with another data model or even with another database connection. You can imagine it’s power and think of the great many of use cases for this! In this blog I’ll describe how the new 12c dynamic components make life easy and I prove you can use just one iterator binding for both ADF business components and POJO data controls.

Changing the session timeout in Webcenter Spaces PS5

In Webcenter PS5 (in contrast to PS4) the session timeout needs to be set in the MDS instead of (or along with) in the web.xml in the Webcenter Spaces ear. If it is not set, the web.xml may be ignored and the server uses the default timeout of 45 minutes due to a bug in PS5.

If the MDS custom parameter is not set, then the following warning appears in the diagnostic log:
“Value of custom attribute wcSessionTimeoutPeriod should be an integer”, even though the value in the web.xml exist.

The solution is to export the webcenter-config.xml from MDS and set the default attribute wcSessionTimeoutPeriod. This can be done with the following steps:

Log in to the linux server and open wlst.
cd $FMW_HOME/Oracle_WC1/common/bin
./wlst.sh
connect('weblogic','','t3://:',adminServerName="AdminServer")
exportMetadata(application='webcenter', server='', toLocation='/tmp/', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')

In another linux shell alter the exported file:
cd /tmp//oracle/webcenter/webcenterapp/metadata
vi webcenter-config.xml

Search for the tag <webcenter:custom-attributes /> and replace with:

<webcenter:custom-attributes>
<attribute name=”wcSessionTimeoutPeriod”>
<description/>
<type>java.lang.String</type>
<value>45</value>
<visible/>
</attribute>
</webcenter:custom-attributes>

Set the value to the desired value and save the file.
Go back to the original wlst console and import the webcenter-config.xml file again.

importMetadata(application='webcenter', server='', fromLocation='/tmp/', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
exit()

If you have set up a clustered environment with more nodes, then you don’t have to repeat this for the other nodes/managed servers. The value is set automatically. The servers don’t have to be restarted.