How to Migrate Custom Soap WSDLs in Oracle WebCenter Content

tekstream blog - custom soap wslds migration

How to Migrate Custom Soap WSDLs in Oracle WebCenter Content

By: Greg Becker | Technical Architect

Oracle WebCenter Content Soap WSDLs can be very useful to expose various WCC services that can be called from a web service request as one of the possible integration methods into WCC. RIDC Java APIs can also be used however in some scenarios, for example where there may not be experienced Java developers on staff, the Soap WSDLs may be the chosen integration method.

A number of out-of-the-box Soap WSDLs available exist that expose common WCC services such as Search and CheckIn. Recently a client that used the ContentFolios component wanted to interact with them using a Web Services approach. Since these particular services are not available out of the box as Soap WSDLs, they needed to be created. We started by creating the new custom Soap WSDLs in a development environment and performed a standard testing cycle.

For more information regarding Customizing WSDL files please check out this link:

After a successful testing cycle, the custom Soap WSDLs need to be migrated to the production environment. After reviewing the Oracle documentation we realized that there isn’t much if any documentation available regarding how to migrate the custom Soap WSDLs from one environment to another. We took a look at the files that are created on the file system when a custom WSDL is created and then came up with the following steps that can be used to handle the migration.

  • Create the new custom Soap WSDLs in your development environment and configure it as you wish:
    TekStream blog Custom Soap 1
  • Next, create a new empty Soap WSDL in your production environment using the exact same name as the one that you created in the development environment:
    TekStream blog Custom Soap 2
  • Copy the file hda from the custom directory in development to the corresponding directory in production. You’ll notice the path below which is typically <domain_home>/ucm/cs/data/soap/custom/:
    TekStream blog Custom Soap 3
  • Choose Action -> Generate WSDLs

TekStream blog Custom Soap 4

Once you perform these steps, the Soap WSDLs should be available in the target environment for use. When the WSDL files are generated, copies of the new custom WSDL file will be moved to a directory within web layout so that they can be downloaded and passed to a developer for use.

I hope that this information is useful for your custom Soap WSDL migration needs. Please ensure that you take a backup of any files that you modify as this approach may not be recognized by Oracle Support, but it has worked as documented for a number of clients. Please contact TekStream if you’d like further information or if you have a similar project need that we can assist with.

Got questions? Contact us today:

[pardot-form id=”14495″ title=”blog – Migrate Custom Soap WSDLs – Greg Becker”]

Using Oracle Records Management for Content Retention | TekStream

records management content retention

Using Oracle Records Management for Content Retention

By: Brandon Prasnicki | Technical Architect

The Oracle Records Management Solution has a powerful Retention Management Process built within it that handles the lifecycle of your content.  The disposition rule workflow is defined at a retention category level.  When content is ingested into the system, the content item can be tagged with the retention category in the form of a metadata field.  With this assignment the content item will follow the disposition process.

The disposition process works as follows:

BP blog behold the legal hold

  1. In general, a content or record item is ingested into the WebCenter Content / Records Management/ Retention Management repository with certain fields (AKA ‘tags’ or ‘metadata’) that describe the content. The content item generally has a filing date or some other date that can be used for defining the retention period of the item.
  2. The item is retained by the system for the defined period of time.
  3. “Something” happens that ends the normal retention period. Either the content item simply met its defied retention end date, or some other user action (‘cutoff’, ‘cancelled’, etc.)  action determines that the disposition approval process should begin.
  4. The disposition approval by the disposition rule approver(s) happens. This can be as simple as a one-step approval to allow the destruction to happen, or it can be complex with multiple steps and prompt the user to first do an approval, create a new revision of a record, notify authors etc.
  5. The defined disposition action occurs. Normally this is Destruction.  However, the Oracle Records Management Solution offers many options for this action including retaining the metadata, only removing previous revisions, archiving to NARA etc.

Now what happens when there is some legal preceding that legally requires your organization to stop the disposition process for some items?

Behold the Legal Hold.  One of the many strengths of WebCenter content management solution is that the Oracle WCC Records Management solution has ‘freeze’ functionality built into the retention management feature.

folder pic bp blog post


Freeze (Legal Holds)

Stops all disposition actions and any deletions or updates



a. Navigate to Records -> Configure -> Retention -> FreezesDefining and applying the legal hold is easy for Records Managers with the appropriate Records rights.

screenshot 1

b. Click ‘Add’ and create the freeze:

screenshot b

Once defined, the freeze can be applied to individual content items from a search (or screen) result, or an entire record folder can have the freeze applied to it.  Within the system, after the freeze (Legal Hold) is applied, you will see a blue pause button indicating the item is held and no further disposition processes will happen.

a. To apply the legal hold, Select the first item and click -> edit -> freeze -> show All Freezes
Select the appropriate freeze and enter a freeze reason. Click OK

screenshot 4screenshot 5

Once the legal preceding is finished, the Records Manager with the appropriate rights, can view the items frozen by this legal hold, and do an unfreeze easily within the system.

TekStream is ready to show you all the features that are available for your retention management and records management solution needs!  Please fill out the form below for a demonstration!

[pardot-form id=”14317″ title=”Blog-Brandon Prasnicki-Oracle Records Retention”]

Defining Your Upgrade and Cloud Strategies: A New Path to Oracle WebCenter Portal

Path Blog Banner

Defining Your Upgrade and Cloud Strategies: A New Path to Oracle WebCenter Portal

By: Kevin Donnelly | Director of WebCenter Portal Consulting

It’s never as easy as the marketing says. Often, a Portal application has so many dependencies that you find yourself stuck in the ground rather than moving up to where you want to be. Priorities lie elsewhere, and you end up with a portal which is up against – or past – end of life, running on old hardware on the verge of being completely unsupported, with no guidance or path laid out on how to successfully move onto a modern platform.

Portal applications are particularly prone to getting caught up in an end-of-life cycle. Typically, a business’s intranet/extranet Portal application serves as a clearinghouse and an aggregation point for a wide variety of different functions – both directly through the Portal, and indirectly through integrations to the backend. This tends to result in the perceived value of upgrades and additional functionality being higher for those endpoints being exposed through the Portal than to the Portal itself; and with any major piece of software, it can fall behind the curve for support. Once that happens, it’s a slippery slope to falling multiple versions behind, paying more for support (or losing support altogether), and turning into a complete legacy portal implementation that no-one wants to touch for fear of breaking the whole implementation.

Unfortunately, crossing your fingers and hoping nothing goes wrong has never been a good IT plan.

If you are in the situation of having a legacy, currently (or soon to be) unsupported Portal implementation, you need to actively consider your path to a more modern, supported, stable platform – both software and hardware. Below are some initial questions typically asked when helping enterprises build their transition path to a more stable Portal implementation.

Infrastructure Approach: On-Premise, Off-Site, Cloud, or Hybrid models?

One driving force behind changes and migrations of legacy software (Portal or not) has always been underlying hardware changes. It’s no coincidence that changes to the support of underlying server software aligned with a number of legacy software migrations. This was seen when Microsoft’s Support for Windows Server 2008 ran out, and it appears to be ramping up again as Oracle’s Solaris 10 leaves Premier Support in less than 9 months. Other considerations are hardware life – owning a physical server means that there will be times when purchasing new servers are necessary – and the simple support appetite for continuing to hardware in-house. More and more companies are looking at a Cloud infrastructure to host their software needs, but question if it’s a good overall fit.

When working with someone to help build that transition path, we find the best by using a solid justification based in true cost and functionality. This includes not just the immediate costs of migration to a new platform, but the ongoing cost of the infrastructure, support of the platform, software licensing (which often differs between on-premise, virtual, and Cloud environments!), and future hardware/software purchases or renewals.

From a functionality perspective, it is important to look at all of your options to be sure you are choosing what best fits your needs. First, choose a category – choose Cloud when you want to get out of the business of owning hardware, and Hybrid when there are applications which can’t move off-premise, etc. What the Oracle Cloud offers is different than what you will get at AWS or Azure; and even within any of these there are significant different options which will result in very different certifications, costs, and maintenance/administrative controls and experiences.

Portal Application Support Approach: Lift and Shift, Migrate, or Rebuild?

As with infrastructure decisions, a good application roadmap requires due diligence and strong planning. One of the characteristics of Portal implementations is that no two are exactly alike – because no two are serving quite the same audience, or have exactly the same needs. That being said, many of the same underlying questions and scenarios continually repeat themselves. There is a tendency to think that since your particular implementation is unique, that the problems you face are unique as well – and that is rarely the case. The first step to planning the future of your existing Portal implementation is taking a good look at not just the current implementation, but your current needs – how have your business needs changed since this was put in place? What new business problems or challenges may have come up? What functionality may no longer exist in a new version or product that would still need to be handled? Is there an absolute need to stay on a particular release due to compatibility issues in the short or long term; and how can that balance with other requirements?

Once the end stage is determined, a good roadmap will be sure to cover the entirety of the path to get your Portal implementation where it needs to be. Environment planning (Dev / Test / Staging, etc.) can give you a path to get a toe in the water of a new infrastructure; but those needs often change drastically in a Cloud or Hybrid environment. Are you planning with the support needs of the current Portal in mind? Are you fully mapping your functionality and your content? The plan also needs to consider the quirks of the legacy system – what customizations and integrations can be reused? How can you migrate the legacy content into a new system?

In the table below, there are a number of common legacy Oracle-based Portal implementations that we’ve worked with, built roadmaps for, and performed migrations on – whether lift-and-shift to a Cloud or Off-Premise environment, or as a fully new Portal implementation. Each of these has some similarities of approach, but also their own challenges to overcome, regardless of the destination.

Portal SoftwareCurrent VersionSupport StatusCommon Implementation Characteristics
WebCenter Portal Server WebCenter Spaces11. (August 2015)Premier Support (ends Dec 2018)• Content and Document Management done via integration with WebCenter Content • Search provided by Secure Enterprise Search or via WebCenter Live Search • Integrations to other Fusion Middleware Platforms • Custom Applications provided via ADF Task Flows • Customized User Interface via Skins and Templates • “Deep” extension of out-of-box tooling typically via replacement rather than extension
WebCenter Portal Framework11. (August 2015)Premier Support (ends Dec 2018)• Content and Document Management done via integration with WebCenter Content • Applications typically included many custom ADF Task Flows • Functionality typically implemented via custom code • Pages were often built within the application and deployed rather than via web tooling
WebLogic Portal10.3.7 February 2016Premier Support (ends Dec 2018)• Most functionality implemented through custom integration and development • Application functionality typically the primary focus of the Portal • Java-based development; typically very customized with complex portlets/applications
Oracle Portal (11g/10i) December 2011 10.1.4 September 2005Sustaining Support (Indefinite)• Heavy custom development, including the PDK and JSR and standards-compliant portlets • Often PL/SQL applications are integrated through out-of-the-box portlets • Generally tight integrations with other Oracle backends
WebCenter Interaction10.3.3 December 2011Sustaining Support (Indefinite)• Integrates to a variety of backends, including custom web applications (Java, .NET and other) • Identity integration typically to an Active Directory or LDAP environment, although users are often managed directly through the Portal • Typically a long-standing portal implementation, exposing diverse applications to its user base • Search indexing in the 10.3.3 version will need regular rebuilds and is often an issue
AquaLogic Interaction6.5 MP1 June 2008End of Life• ALI 6.5 is fully out of support, so typically companies will have either good internal knowledge of the system, or it has remained stable for some time. • Integrates to a variety of backends, including custom web applications (Java, .NET and other) • Identity integration typically to an Active Directory or LDAP environment, although users are often managed directly through the Portal • Typically a long-standing portal implementation, exposing diverse applications to its user base

If you are running on any of these platforms and are looking to move to a modern platform and/or a Cloud-based implementation; feel free to reach out to TekStream Solutions for a conversation, or check out the TekTalk webinar replay: Upgrading WebCenter Portal to the Cloud.  We’d be happy to talk to you about your plans for Portal migration, and how to best put you on the path to success.

[pardot-form id=”13937″ title=”Blog-KevinDonnelly-Path”]

Using Records Management Solutions To Handle WebCenter Content Requirements


Using Records Management Solutions To Handle WebCenter Content Requirements

By: Brandon Prasnicki | Technical Architect

Oftentimes there are requirements customers have that have the feel of customizations, but actually can be handled by out of the box functionality with Records Management (or in the simplest WCC form this feature can be referred to as ‘Retention Management’) functionality. Oracle WCC has a records management solution that has features that are obvious (disposition, audit, metadata history, etc.), but it also has some features that may be useful for core WCC requirements that might otherwise be costly customizations. Here is a list of a few of three of these common requirements:

  1. Global updates via the UI
    1. WebCenter Content Management solution (with records management disabled): can do this with folder propagation and archiver but anything query based via the UI is a customization
    2. Retention Management solution: A Global Updates submenu within the main Records menu is available when the appropriate RM rights are assigned
  2. Security Restriction based on Revision, Metadata updates and Delete
    1. WebCenter Content Management solution (with records management disabled): there would need to be some custom component that would hook into service to see if user had a role that allowed revisioning and/or metadata updates to restrict beyond normal RW access. Also a UI customization to disable the checkout/check-in would be needed.
    2. Retention Management solution: RM restriction flags can be set on the definition of a category, and when content is assigned to this category via metadata, the restrictions are in place. Then the appropriate RM rights can be assigned to these users with special permission to perform these functions. *Note that records categories don’t need to have disposition assigned, and categories can be assigned by deriving the xCategoryID field with a profile rule.
  1. Review
    1. WebCenter Content Management solution (with records management disabled): Some customization to trigger a scheduled event based on a review date and query, or some basic workflow needs to be manually generated
    2. Retention Management solution: There is out of the box functionality that marks an item ‘vital’ and users responsible to do the review are emailed assigned to do the review with a review action.


  1. Global updates

Global updates is an out of the box feature available in records management for users that have the ‘search and update’ and ‘no security’ RMA right.

retention management 1

When RMA rights of ‘Search and update’ and ‘No Security’ are assigned to a role, these users will see a new records menu item called ‘Global Updates’ where they can use a query based form to update values en masse.

retention management 2

When building the query, you can preview the results and even schedule the run if it is a large job.

retention management 3

  1. Security Restrictions

When creating a retention category, the following security restrictions are available:

retention management 4

The restrictions can be defined as follows:

  1. Restrict Revisions: All content in this category cannot be revisioned by users whom do not have the RMA Right of Record.Revise (even if they have WCC write access).
  2. Restrict Deletes: All content in this category cannot be deleted by users whom do not have the RMA Right of Record.Delete (even if they have WCC delete access and are author).
  3. Restrict Edits: All content in this category cannot have the metadata updated by users whom do not have the RMA Right of Record.Edit (even if they have WCC write access).
  4. Transfer or Accession to NARA (AKA ‘permanent’): No revisions, deletes, edits are allowed even for users with these RMA rights.

retention management 5

         3. Review

When the Records management solution is leveraged (Retention Management is enabled), there are new fields on the form that are available. Simply check the vital flag and fill out the reviewer and period information, and this user will get an email to review the item!

retention management 6

TekStream is ready to show you all the features that are available for your retention management and records management solution needs! Please fill out the form below for a demonstration!

[pardot-form id=”13891″ title=”Blog-BrandonPrasnicki-RecordsManagementSolutions”]

BPM Document Integration with Content Management Framework Folders

Business process management

BPM Document Integration with Content Management Framework Folders

By: John Schleicher | Sr. Technical Architect

Oracle BPM (workflow) of both BPMN and BPEL flavors offers document integration as basic functionality as well it should. Human workflow is inherently tied to documents that support the activity in question. To provide this capability workflow accommodates documentation (aka attachments) in task based schemas and within the User Interface forms that support it. Workflow programs can pass documentation to tasks by carrying them in the schema as files or URL references. The BPM form documentation component then exposes those documents for viewing and allows for the addition and deletion of the same.

The default storage of the documents is made within the underlying workflow database schema but administrators can configure the workflow engine to leverage the content management data store as an alternate location. Information about this can be found in the SOA Administrator’s guide and numerous blogs.

The content storage alternative offers storage improvements over the original configuration but still is fairly limited in ability as compared to interacting with documentation within the content system itself. Though the ability to view existing documents, add or delete documents and define a few optional criteria exists with the BPM based user interface, more sophisticated elements of content such as managing revisions or viewing history are not available. You can also search for content documents and attach them to the workflow through the BPM attachments UI component. This may offer some integration but ultimately requires the users to be accessing both content and BPM interfaces in a fairly disjoint fashion to be somewhat effective. Shouldn’t there be a more effective mechanism?

When faced with a requirement to migrate a manual workflow system based on file folders the answer became obvious. If the workflow documentation was segregated into logical folders within content (basically into framework folders) then workflow could access the content UI based on that workflow associated folder. So instead of using the existing BPM document component, the URL specifying the framework folder was substituted as a go button or link in the BPM form which would render the content UI for that folder with the document listing. Adding new documents can likewise be provided by another go button tying it to the Add capability of the content URL so the users can click a button, add a title, browse and upload a document to the folder and workflow.

There was initially some concern over the lack of a document listing on the BPM form. The concern was easily allayed however by the common activity of separating the tabbed content document listing from the BPM form and simultaneously displaying it on a dual monitor system. Power users have ready access to the document listing with this configuration (as shown in the below diagram). Also the separation of the listing offers more real estate for the rest of the form. For my case I extended the comments component into the vacated space formerly reserved for the list of documents.

There are other benefits to leveraging the content UI straight from workflow. The first of course is the ability to leverage document versioning. Secondly, document access beyond the workflow lifespan is easily possible, as well as applying search metadata against the folders and documents to allow non-workflow association to be realized. For the out of the box workflow/content integration when workflow is complete, how do you get to those documents? For the direct integration outlined here, you are already creating the folder, so you can also apply some metadata for searching folder contents and you have the ability to find workflow documentation well beyond the life of the workflow.

This new configuration has some coordination required between workflow assignees and content roles. Workflow users require sufficient privileges to view, add/delete, and update content. This administration is simple enough and can be tied to the framework folder that is associated with the root element for the workflow activity.

So what could be classified as a drawback? For one, the simplistic ingestion of documents into the storage requires a bit more programming. The workflow system (whether BPMN or BPEL) must now leverage the UNIVERSAL_CREATE mechanism of content’s GenericSoapPort webservice to create logical folders for the workflow and then create/upload any documents coming into the workflow. The logical folders must be oriented around a unique key to be able to reference the folder throughout the workflow as the form must provide the specific folder’s URL for access of documentation. Also applying metadata for post workflow searches is a small overhead as well. So ultimately this is a little more complicated than the original but not prohibitively so.

So I have outlined a relatively straightforward integration of Oracle BPM and Content storage for workflow documentation. If your BPM project is aligned on folders or another logical key it may be an option for your documentation access.

BPM Workflow tab adjacent to Content Framework Folder Listing

BPM Workflow

Have more questions? Contact TekStream today!

[pardot-form id=”13871″ title=”blog-BPMDocumentIntegration-johnschleicher”]


Using Business Objects With the Oracle Process Cloud Service

Young businessman with big blue cloud

Using Business Objects With the Oracle Process Cloud Service

By: Courtney Dooley | Content Developer


Imagine you’re outlining an Oracle Process Cloud Application that you need to build. You then realize you need the data that’s entered into your form to be passed to a Process, filtered through a Decision, and used as an input for a REST API call.  That scenario could have you creating a Field, Data object, Decision input object, and a REST API request body.  However, if you start by defining a Business Object that contains all the data you will need for these functions, you may find you only need one.  Below describes how you can keep your data organized within your Process Cloud Application, and shorten the time needed to create and link these objects. Oracle PCS is extremely versatile and can help you leverage the Oracle Process Cloud optimally.

Creating Application Wide Business Objects With Oracle PCS


  1. Define your Business Object to Allow the Most Versatility

A Business Object is a set of data you will be storing throughout your process.  It may be two or three string values, a combination of dates, amounts, and personal data. Or, it may be a complex set of arrays.  Business Objects can take many forms which allows for a wide range of business needs.  The key for success is to have a versatile Business Object to avoid creating new Business Objects for data at different points in your workflow process.

For example, you want to create a form that will ask for a user’s name, address, phone number, and email.  From this you will derive the user’s region where you can then perform a lookup to get the user’s account number.  A shorter process, rather than having a Form Object with field values, a Decision Object for the region derived, and then an API Request Body to do the account lookup; it is best practice to create a single Business Object with all six values defined within it.  Make sure to specify that account number is an array as the user may have more than one account.

  1. Create your Business Object in your Process Cloud Application

There are multiple ways to create business objects within the Process Cloud

Creating New Business Objects

This option does not require any code or formatting and will walk you through creating your Business Object, step by step.  For details on this option, Click Here.

Business Objects 1

Importing Business Objects – From XML Schema

If you have an xsd file for a web service you will be using, or if you have an XML Schema already written, this option allows you to import that file to define your attributes.  For more information on this feature, Click Here.

Business Objects 2

Importing Business Objects – From JSON

If you know you will be using a REST API call within your process, this option allows you to paste in the JSON that will define your request body.  You can also write your own JSON to define what attributes you will be using in this Business Object.  Simply format your attribute as outlined below. The values are examples of the types of values you are expecting.

“Name” : “Your Name”,

“Phone_Number” : “123-555-9876”,
“Address” : “123 Baker St, New York NY 54321”,
“Email” : “”,
“Account_Number” : [{
“Account_Number” : 123123

“Account_Number” : 234234


Business Objects 3

  1. Using Business Objects

Now that you have your attributes defined in your new Business Object, you can create a form in a snap.  Whether you’re creating a Web Form (Oracle’s newest form builder) or a Basic Form (Frevvo), you can drag and drop your Business Object into your form and have the fields built out for you.  Just follow the steps below:

Web Forms:

  1. Create a New Web Form, or Edit one you’ve previously created.
  2. From the Business Types Palette, drag and drop your new Business Object
  3. Business Objects 4All of the fields will appear as you outlined in your Business Object, including the ones your user will not be filling out.
  4. Business Objects 5Now you can modify the fields to the layout you prefer. You can also remove the fields you don’t want on your form.

Basic Forms:

  1. Create a New Basic Form, or Edit one you’ve previously created.
  2. Click on the Manage Business Objects Business Objects 6 icon in the Form Header menu.
  3. In the Form Business Objects window, move your Business Object from the “Available” Column to the “Selected” Column.
  4. business object aAfter clicking “OK”, your business object will be available in the Data Sources Business Objects.
  5. business object bYou can either click the green plus sign for the individual objects you wish to add to your form, or you can click the green plus sign for the entire object to create all fields.
  6. business object cNow you can modify the fields to the layout you prefer, as well as remove the unwanted fields.
Processes, Decisions, and Integrations

Throughout your application development process you will find many places where you need to define the type of input and output you will be expecting.  Now that you have defined your Business Object, it can be used for any data object input or output.

Sub Processes:  Inputs and Outputs

business object d

Decision Rules: Inputs and Outputs:

business object e

Integrations: Request Body and Response Body

business object f

As you can see, Business Objects can unify your Application Data and can significantly speed up the development process.  By planning ahead and making smart choices for your Business Objects, you can create a complex Application simply.


Contact Us for more tips and tricks on developing smart Oracle Process Cloud Applications or general use cases for the Oracle Process Cloud.

[pardot-form id=”13489″ title=”PCS Blog – Courtney”]

Oracle’s Hybrid Cloud Approach between WCC and Docs is available and easy to configure.

Cloud Hybrid

Oracle’s Hybrid Cloud Approach between WCC and Docs is available and easy to configure.

By: Brandon Prasnicki | Technical Architect

The Oracle WebCenter Content to Oracle Documents Cloud hybrid solution has unofficially been around for a while, but I haven’t personally seen it as an ‘Oracle Product’.  Last year, Peter Flies wrote a blog on incorporating Oracle Documents Cloud into the native UI using the REST API.  You can see that blog post here:

In February of 2016, Cordell and Thrond from Oracle support conducted their own presentation:  In the recording or in the slide show (see slide 33 here: you can see an informative screenshot of the ADF content UI with Oracle Documents Cloud folders built right into the interface, creating a hybrid cloud solution.  I’ve been waiting for that particular hybrid cloud solution, and now it’s available!

Recently, while doing a demo of WCC (Version: 07:41:00Z-r148019 (Build: running on Oracle’s cloud compute environment, I ran across a component called Oracle Documents Folders.

I enabled this component in the native UI and restarted.

Cloud Hybrid1

After restarting, I saw a new menu in the Administration menu:

Cloud Hybrid 2

I configured the Oracle Documents Cloud Service information.  However, once I received a hostname verifier error, I had to disable it in the WLS admin server (Consult IT to verify if this is acceptable for a production environment).

Cloud Hybrid 3

After testing and then saving, I restarted the WLS admin server, the WCC server, and the ADF content UI.  I logged in as a test user and verified the preferences:

Cloud Hybrid 4

Note the message regarding the link between Oracle Documents Cloud Service and WCC.  In order to make the hybrid cloud solution work, the email address in WCC needs to match the Oracle Documents Cloud Service username.
After that was complete, I was able to navigate under an Enterprise Library and create an Oracle Documents Cloud folder.  This instantly showed in my cloud environment. From there, I could drag and drop items into my Oracle Documents Cloud folder right from my WCC ADF UI, and vice versa.

I now have a window into my Documents Cloud interface right from WCC using this simple hybrid cloud solution.  It is now easy for me to search and find a template or a form in WCC via the ADF UI, download it and then put it in the Oracle Documents Cloud.  Right from the UI, I can also share the document via a public link within seconds.  Once a cloud user edits that document and uploads it again, or adds more content, the hybrid cloud solution makes it instantly available in the context of my browsing experience of WCC.

On the Oracle Cloud Document service side, it creates the folder with the username in the path:

  • Documents > Mary > A312D3148815662CA5B70F9F837EDFB0 >BrandonTest

Cloud Hybrid 5

It’s pretty easy to set up, but if it’s even quicker to let us show it to you!


Contact TekStream or Brandon Today to Learn More.

[pardot-form id=”13211″ title=”Cloud Hybrid Blog – Brandon”]

Expanding the Expired Search Functionality in the WebCenter Content (WCC) Native UI

Search WebCenter

Expanding the Expired Search Functionality in the WebCenter Content Server Native UI

By: Brandon Prasnicki | Technical Architect

In the past customers have complained about the limited search feature related to expired content.  Normal users, and especially power users, may have a need to retrieve an expired content item but cannot easily recover or locate it.  This may discourage users from using the expiration feature in WCC. As you may know, when expiring an item, the content is kept in the system. However, in the case of Oracle Text Search Engine, pull the item from the collection to reduce the search collection size.  This can help with collection builds (including fast rebuilds) and search speeds.

While many of the WCC user base is transitioning to the new sleeker content UI, it is not uncommon for power users to continue using the native UI for more complex functions.  An example of a complex function is locating expired content.  In order to do a search for expired items, a user will navigate to Content Management -> Expired Content.  In the screen shot below, the user is presented with two date fields to filter the recently expired items.  If there are many expired items, or the time frame of the expiration is not known this is not very helpful.

wcc content 1

How can this process be simplified for the user? A simple customization is in order!

Introducing the TSExpiredSearch component: This component adds a button in line with the other buttons that users normally use.  This button switches the repository and goes after expired content items instead of the OTS search repository (or other active content item repository).  You can use the standard search, profile search and even query builder pages and leverage the expired search functionality as this new ‘Expired Search’ button is added to a common resource where the out of the box buttons are seen.  With the button in place, the normal metadata fields can be leveraged and all the existing rules and profile logic is in place to help the user locate the expired content.

wcc content 2

wcc content 3

The expired search feature leverages the Repository parameter and sets it to ‘ExpiredContent’.  The generated query uses the search engine: ‘DATABASE.METADATA.ALLDOCS.ORACLE’. Therefore, the user must use ‘Matches’ and not run Full-Text Searches.  This validation is included in the component, as shown below:

wcc content 4

This component has been tested on,, and  It even fixes a breadcrumb bug in  If you would like to use it we’d love to give it to you!  Please fill out the contact form below and we will send it right away.

Once you receive your component, you will need to install and enable it using the admin server –> component manager -> advanced component manager options.  Hopefully this will improve user search experience and even encourage users to clean up the active collection.


Fill out the following form to download the TSExpiredSearch component:
 [pardot-form id=”13151″ title=”Expired Search Blog – Brandon”]

Creating a Single Item Content Presenter Template in WebCenter Portal 12c (12.2.1)

Computer Programming WCP

Creating a Single Item Content Presenter Template in WebCenter Portal 12c (12.2.1)

By: Abhinand Shankar | Technical Architect

The WebCenter Portal (WCP) implementations I have worked on include an integration with WebCenter Content (WCC). WCC managed the creation of the content items through Site Studio. WCP handled the presentation that covered the content on the web page that was finally rendered. This was done through Content Presenter Templates.

In 11g, the round trip development of the templates involved downloading a DesignWebCenterSpaces application that was preconfigured for managing the assets. The release of 12c brought changes to this process. JDeveloper is now built in with the application template to create the portal assets.

When creating a portal asset project, you have the option to select the asset type as Content Presenter Template.


This generates the project and all the necessary artifacts.


In this example, SampleContentPresenter.jsff contains the actual code. You can deploy the asset to the portal managed server directly from JDeveloper or create an AAR file and upload it. It is now available when configuring a Content Presenter task flow on the portal.


You will notice that the template is available only when the content source is a list of items and not for a single item. A look at assetDef.xml shows that it is created as a list template by default.


The application creation wizard does not give you an option to select the type of template. Therefore, attempting to update assetDef.xml throws an error.

In order to create a presenter template for a single item, create the application with the defaults and deploy it to the managed server. Log into portal administration and from the assets page download the template. Explode the archive and you should see a file called asset-entities.xml under the folder contentPresenter-s-gsr90079447_922e_48ff_a483_0c496a20c1c9 (the folder name contains a guide).

Asset-entities.xml contains the definition for the template and is by default as shown below:


Update this section as follows:


Make sure to update the jsff file to use the tag for a single item content presenter template.


Archive the files and deploy the AAR file. The template should now be available for a single content item.


Note: After deploying the template, you may have to uncheck the available box and then check it again before it shows up in the drop down.


Contact Abhinand or TekStream Today

[pardot-form id=”13113″ title=”Content Presenter in WCP Blog”]