Entries in oracle webcenter portal (2)


Registering WebCenter Portal Custom Taskflow 

These steps are only needed if for some reason like I find a conflict or a mapping problem occurs and the task-flow-registry.xml file is the not picked up by the portal meta data management service.

After you create your own bounded taskflow, register and deploy to your webcenter portal weblogic server.

Look at your taskflow definition from your bounded taskflow in the below example my definition is called customflow.xml. Then find your id of your taskflow mine is customid then use this to fill in the url attribute example would be “taskflow://WEB-INF/customflow.xml#customid”.

Change up the value fields as you wish for display purposes when you add the following task to the Resource Catalog.

### example entry ##

 <folder id="newfolderid">

            <attribute attributeId="IconURI"
            <attribute attributeId="Title" value="My Custom Taskflows"/>
id="customtask" name="customname" url="taskflow://WEB-INF/customflow.xml#customid">
                  <attribute attributeId="Title" value="Custom Taskflow Title"/>

## end of example ##       

After you change the above xml to match your taskflow definition log in as an administrator in your webcenter portal. Then go to the Resource tab and click on the Resource Catalogs item under the Structure section.


1. If you have not already you need to copy the Default Space Catalog and name it what you want.

2. Then select the new catalog and click the edit button then select edit source.

3. Find an existing url tag and paste your changed above xml from folder to folder tags above one of the existing url tags.

4. Then just change your default resource catalog for the space you want to use your new taskflow.

Picture of added folder in visual edit mode of the resource catalog view.

 Here is a picture of the finished component added to my personal space page.


WebCenter Portal Restful Services Setup PS4 and PS5


Here is the original document from Oracle but I have added a little more steps to help clarify the setup.

Original Instructions

All of the REST APIs, except for the navigations REST API, require WebCenter Spaces. For information on the navigation REST API, see Section 13.3.2, "Using the Navigation REST APIs."

51.2.1 Introduction

Before you can use the WebCenter REST APIs, you must perform the server-side configurations described in this section. You must perform two separate configurations. You must configure an identity asserter and you must seed required entries in the credential store, which enables the REST security tokens to function properly.

Perform these configuration tasks when WebCenter Spaces is installed for the first time or if you otherwise know the configuration tasks have not been previously performed.

For more information on security tokens, see Section 51.9, "Security Considerations for WebCenter REST APIs."


This configuration is not required for the navigation REST APIs or for the CMIS REST APIs.

51.2.2 Configuring an Identity Asserter

First, you must configure an identity asserter before using the REST APIs. For detailed instructions, see "Configuring the REST Service" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.


 Here the start use your own admin password do not change anything even the copied instructions use verbatium.

First do this to see it not working in a browser hit the url localhost:8888/rest/api/resourceIndex put in you userid:youruserid and password yourpassword

Now after all this you will see all the xml just follow the steps.

WebCenter Domain Keystore

  1. Go to JDK_HOME/jdk/bin 
  2. RUN THIS COMMAND: keytool -genkeypair -keyalg RSA -dname "cn=spaces,dc=example,dc=com" -alias orakey  -keypass welcome1 -keystore default-keystore.jks -storepass welcome1 -validity 1064
  3. RUN THIS COMMAND:keytool -exportcert -v -alias orakey -keystore default-keystore.jks -storepass password -rfc -file orakey.cer
  4. RUN THIS COMMAND keytool -importcert -alias webcenter_spaces_ws -file orakey.cer -keystore default-keystore.jks -storepass yourpassword
  5. Ensure that the default-keystore.jks keystore file is copied to the <DOMAIN_HOME>/config/fmwconfig directory, and then specify the location as ./default-keystore.jks.
  6. Open Fusion Middleware Control and log in to the WebCenter domain.
  7. In the Navigation pane, expand the WebLogic Domain node and click the WebCenter domain (wc_domain by default).
  8. From the WebLogic Domain menu, select Security -> Security Provider Configuration.
  9. Expand the Keystore section on the Security Provider Configuration page
  10. Click Configure

Description of "Figure 32-4 Keystore Configuration Page"

11. Use the following settings to specify the location of the keystore that contains the certificate and private key, and the signature key and encryption key aliases:

  1. Keystore Path: 
  2. Password
  3. Key Alias: orakey
  4. Signature Password
  5. Crypt Alias: orakey
  6. Crypt Password

12. Click OK to save your settings.

13. Restart the Administration server for the domain.


28.8.3 Configuring the WLS Trust Service Asserter

This section describes how to configure the WebLogic Server Trust Service asserter.

To configure the WebLogic Server Trust Service asserter:

The Create a New Authentication Provider page displays.

  1. Enter the Name of the new asserter (for example, TrustServiceIdAsserter).
  2. Select TrustServiceIdentityAsserter 

This asserter calls the Trust Service APIs to decode and validate the token from the incoming request, and pass the username to the WebLogic for establishing the asserted subject.

  1. REBOOT everything again




wlst.cmd in the ECM directory common/bin

connect(‘userid’,’password’, ‘localhost:7001’)


createCred(map="o.webcenter.jf.csf.map", key="keygen.algorithm",

    user="keygen.algorithm", password="AES")


THIS ONE told me it already exsisted after running it no harm no foul it worked

createCred(map="o.webcenter.jf.csf.map", key="cipher.transformation",

    user="cipher.transformation", password="AES/CBC/PKCS5Padding")


OK you are done lets test it out :-) 

 In a browser hit the url localhost:8888/rest/api/resourceIndex put in you userid:myuserid and password yourpassword when prompted by browser.

Try the RestConsole for chrome