Note: This is a very roughly put-together guide. I will spend some time in cleaning this up later.
I had someone ask for help on deploying a task flow to WebCenter Spaces and exposing it through a resource catalog. Here’s a quick run-through of how I do it. I will explain the essential building blocks and you should be able to implement it any way you like.
What you’ll need
1) Read the “Extending WebCenter Spaces” whitepaper on OTN.
2) Download the sample project that supplements the whitepaper.
Both these can be downloaded from OTN here. The easiest way to expose custom ADF task flows is to use the sample project and the ANT build file it contains. You can always customize the project to fit your requirements.
1. Shared ADF Library
- Develop your ADF Taskflow and create an ADF Library out of it.
- Create a new WAR file (let’s call it custom-taskflow.war) including the ADF library jar(s) from step 1 in the WEB-INF/lib of the WAR. Optionally include a manifest to name your extension and setup version info.
- Deploy the WAR to the weblogic server to the WLS_Spaces and AdminServer managed server as a shared library. Note the deployed library’s name from the WLS Admin Console.
2. WebCenter Spaces Customisation
To expose the custom task flow in the Spaces catalog, you have to create and deploy a customisation shared library – “custom.webcenter.spaces”. The Webcenter Spaces installation should already contain a base version of this library.
Here we create and deploy a WS customisation that makes the task flow available on the Spaces catalog. You may choose to add the task flow to either the default personal catalog or the group spaces catalog.
- From the whitepaper sample project, copy the resource catalog required. You’ll find them in the path SourceFiles\catalog\oracle\adf\rc\metadata\scopedMD\defaultScope
- Edit the xml file and add your custom task flow to the resource catalog. To obtain the correct entry for your task flow
- Create a file system connection to the folder containing your ADF Library Jar (from Step 1a)
- Navigate to the task flow entry in the file system connection
- Right clock on the task flow and choose the option “Show Catalog Reference”
- You can copy the entire XML tag that shows up in the dialog.
- Optionally you can add attributes to this – title, description, etc for your task flow. See the entries already present in the source catalog for reference.
- Create a jar that contains the resource catalog. The path to the catalog in the JAR should be custom\oracle\adf\rc\metadata\scopedMD\defaultScope
- Create a WAR file to deploy this as a shared library. A few important points to note on this
- The WAR should contain the JAR from 2c in WEB-INF/lib
- The WAR should contain a weblogic.xml with a library reference entry pointing to the deployment name from 1C.
- The WAR should contain a manifest file that specifies the following mandatorily (See the sample project for reference)
Specification-Version: <the specification version of the default custom.webcenter.spaces library>
Implementation-Version: <an implementation version higher than the current deployment>
- Deploy the WAR file as a shared library to the WLS_Spaces and AdminServer managed servers.
- Redeploy the webcenter application on WLS_Spaces for the changes to take effect.