WebCenter Content customers – now that Google has announced the discontinuation of their Google Search Appliance, are you looking for a proven, lower-cost alternative?
Redstone has the solution for you!
During this webcast, Redstone will provide an overview of our Distributed Index and Search UI solution. We’ll demonstrate how your organization can seamlessly transition away from the GSA. You’ll be able to provide your end users with a great search experience at a lower cost.
Additionally, you’ll hear from special guest Be The Match operated by the National Marrow Donor Program and their journey from the GSA to Distributed Index.
Product Owner/Business Sponsor
Manager, IT Enterprise Application Systems
What You'll Learn:
WebCenter Sites can be integrated with a variety of Digital Asset Management solutions. Did you realize that you can also create a simplified solution right within WebCenter Sites? Now is the time to understand all your DAM Options! Learn about Oracle offerings, offerings from other vendors and options you can develop on your own!
For all your Oracle WebCenter needs, Contact Redstone Content Solutions: We Deliver.
For years, Oracle has been empowering marketers with next generation tools like WebCenter Sites and Eloqua.
In 2015, Oracle plans to bring the two powerhouse solutions together!
Oracle aims to provide unparalleled marketing power to customers by integrating WebCenter Sites with the Oracle Marketing Cloud. The first phase of the WebCenter Sites and Eloqua integration will be included in WebCenter Sites 220.127.116.11.0 Patch 10.
WebCenter Sites and Eloqua specialize in enabling non-technical marketing users to easily deliver engaging experiences on the web and through email. By integrating WebCenter Sites with Eloqua, Oracle is no longer focusing email campaigns or web experience as individual marketing channels, but as one continuous digital experience.
The goal of all marketing teams should be to ensure a seamless and consistent digital experience for visitors crossing between campaign channels and the main website. This can be achieved in the following ways:
Sharing content across channels & personalizing email content
Eloqua email authors can drag-and-drop WebCenter Sites content on Eloqua emails and landing pages to ensure consistency of the marketing message and seamless visitor experience across channels. By passing visitor profile information from Eloqua to the WebCenter Sites cloud application, marketers can send personalized email with content sourced from WebCenter Sites thereby enhancing the visitor experience.
Eloqua includes form building capability, used to capture lead-generation details from visitors. These lead generation forms can be placed on WebCenter Sites delivered pages through drag and drop placement. WebCenter Sites ‘Cloud asset’ feature enables externally hosted content to be accessed from within the WebCenter Sites Contributor User Interface. The forms appear in WebCenter Sites search and browser interfaces and can be dragged and dropped onto Sites pages.
Redstone Specialized & Ready for Action
Two years ago when Oracle purchased Eloqua, Redstone made a post in a LinkedIn Group asking the question, “How long until Oracle integrates Eloqua with WebCenter Sites?” We now have our answer: two years. The good news for our customers is that we asked that question two years ago, and it is that forward thinking mindset that has Redstone prepared for what’s coming next.
In 2013, we began focusing on WebCenter Sites and in January 2014 we became the first partner worldwide to become Oracle Specialized in WebCenter Sites. Additionally, we began creating our Digital Experience (DX) Gateway solution in 2014. DX Gateway is an enterprise class jump-start program that automates the installation, configuration and deployment of best practice, multi-tier WebCenter Suite environments.
For Additional Information
Please refer to the attached documentation for more details.
In addition, there is a new A-Team blog that mentions how to architect the Oracle stack for a modern marketing sales funnel:
For all your Oracle WebCenter needs, Contact Redstone Content Solutions We Deliver.
Training Course Details
Date: Monday 1/19/2015 – Friday 1/23/2015
Duration: 5-Day Course
Time: 8:30am – 4:30pm each day
Location: Marshalltown, Iowa
Contact Redstone for:
About the Training Organization
For more information please contact Michael Lawrence from Redstone Content Solutions
Written by: Adam Stortz
Recently we received an email from an avid reader of Core Content Only, Brian. He was inquiring about an error message he received while attempting to develop a service within WebCenter Content 11g and how to go about fixing it. The error message giving him trouble was “Content Server Request Failed” and will appear as such.
Typically this error message is thrown during the integration of a custom component developed for an older version of Content Server onto 11g. In this scenario the authorization token (“idcToken”) is not being passed from the component to a subsequent service request resulting in the error message being thrown.
We've encountered this error in the past and we were able to uncover a few solutions. To help other developers encountering the issue save time and correct the issue, we have provided our solutions below. Before we are able to correct the error, first we must understand the error.
What is this authorization token, and why do we need it?
The authorization token is a security feature with in WebCenter. The authorization token is automatically generated and assigned to the user during each session. The token’s purpose is to maintain the ‘State’ of the user in the new state-full architecture of WebCenter Content 11g when passed along.
Service parameters allow users access to content based upon authorization levels identified by the token. The authorization token communicates the level of access based on context and user information to WebCenter.
What does it mean when the Content Server Request Fails?
The Content Server Request Failed error message happens when the authorization token is not passed along. The Authorization Token may not be passed along because it is either missing or expired.
When working through a solution it is important to note that the actual error being encountered is !csInvalidAuthorizationToken
The solutions to the missing Authorization Token are covered below.
Solutions for the Content Server Request Failed Error
The Content Server Request Failed error message offers little information on how to solve the issue. The only solution suggested by the default error message is to “Try reloading the page”.
Rarely will reloading the page solve the issue and the same error message will be thrown. Reloading the page will only solve the issue if the issue was with the page load. A missing authorization token cannot be fixed by reloading the page.
There is no need to panic if this is the case; there are other solutions that we will walk you through. Below are three alternate solutions not mentioned by the default error message that will correct the issue with the missing token.
The solutions below will show a small component using 2 services (MyCustomService and MyTokenService) and 1 template to help visualize the concepts.
Solution 1 - Setting the service to scriptable
Solution 2 - Include Token in Service Calls
First place the idcToken into the parameter list of the service. This is done by editing the HTML page being rendered on the page, like so.
This will place a button or link to the service in question, MyCustomService, with the current idcToken. The end result will be displayed as such.
Solution 3 - The Authorization Token can be disabled
The authorization token is a security feature and disabling it is not a recommended option, but if you are on a development instance it might be useful.
This can be done by adding the variable DisableAuthorizationTokenCheck=true into the \ucm\cs\config \config.cfg file. By default the option is set to false.
Services calls are not the only instance where this error can occur. This error may happen to the hypertext content server forms (HCSF). Although HCSFs differ from services the error can be resolved using solution two from above.
The only difference from solution two is the syntax of the template. In an HCSF an IdocScript snippet must open with <!--$ and close with --> so the entire snippet of code will look like <input name="idcToken" value="<!--$idcToken-->">
We hope you have found our solutions to the Content Server has Failed error message useful and time saving. If you have any feedback, comments or concerns please let us know, and comment below.
If you are having other issues, please identify them in the comments below or through our contact form and we will make sure to address them in an upcoming blog posts.
Written by: Jason Stortz
Oracle WebCenter Content (abbreviated WCC and formerly referred to as UCM or Stellent) exposes nearly everything it can do as a service. WCC is very SOA friendly. We can take advantage of this fact and use something like curl or wget to execute services in WCC from the command line.
While curl and wget are often thought of as Linux/UNIX/OSX commands we should point out that there are versions that can be installed for Windows as well. The official description of curl:
Curl is a command line tool for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, Gopher, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, Telnet and TFTP. curl supports SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user+password authentication (Basic, Digest, NTLM, Negotiate, Kerberos…), file transfer resume, proxy tunneling, etc.
Curl offers many useful features like proxy support, user authentication, FTP upload, HTTP post, SSL connections, cookies, file transfer resume and more. We can use curl to script calling services in Oracle WebCenter Content.
First Example - PING_SERVER
Oracle WebCenter Content has a simple service named PING_SERVER that you can execute to see if the Content Server is actually alive, listening and processing. You can find out more about PING_SERVER by looking in at the Oracle WebCenter Content Services Reference Guide.
To execute the service with curl from the command line there are three basic parts to be typed in:
With this in mind we will pretend we have a Patch Set 5 instance of Oracle WebCenter Content running on a machine named PS5. The command to execute PING_SERVER against that machine would look like:
curl http://weblogic:welcome1@ps5/_dav/cs/idcplg -d "IdcService=PING_SERVER&IsJava=1"
Second Example - Workflow Testing
Creating a Workflow in WebCenter Content has a few interesting caveats and testing the Workflow you've developed is very important. Manually testing the workflow can be a cumbersome process. A small script that executes a series of curl calls to Content Server can make the testing process a lot smoother.
You can create scripts that test the various paths a piece of content might take through the workflow. Here is an example of a curl call that will approve a document currently in workflow and advance that document to the next step. If the document is at the end of the workflow this would cause it to exit workflow and be released for consumption.
curl http://weblogic:welcome1@ps5/_dav/cs/idcplg -d "IdcService=WORKFLOW_APPROVE&dID=1268&IsJava=1"
Oracle WebCenter Content References
What is the sysadmin user for in WebCenter Content 11g?
The primary administrative user ID in WebCenter Content 11g out-of-the-box is the weblogic user. This user and password is created when the WebLogic Domain is created.
So what is that sysadmin user in the User Admin Applet? And what is the sysadmin password?
Out-of-the-box WebCenter Content uses the Oracle WebLogic Server User Store to manage user names and associated passwords. Typically, user management is handled in the Oracle WebLogic Server Administration Console instead of the WebCenter Content User Admin applet. If you create a user only through WebCenter Content User Admin Applet Oracle WebLogic Server does not recognize that user. These kinds of users are called local users.
The sysadmin user can be used to run the stand-alone administration applets. Before you can do that you need to use the User Admin Applet to change the default, randomly encoded password that the sysadmin user is created with.
You might also create local users for integration activities like web service calls or using UXIdcCommand.
I wanted a keyboard shortcut for an elevated command prompt but just could not seem to find a way to accomplish it with less than three different key combinations. Some suggestions came close by using the new Power User menu in Windows 8, but still required you to execute “Win+X”, then press “A” for Admin, then accept the UAC Prompt. I found a way to get rid of one of these steps.
So in Windows 8 I wanted to run an elevated command prompt. After looking around on the Internet I couldn't find any examples that really did what I wanted to, so I decided to try this. I'll press the "Start" key to bring up the start menu, and I'll start typing "cmd" for command. Right click the command prompt, and select "Open File Location." Copy the command prompt and rename it "Command Prompt Admin." Right click on this new shortcut and select "Properties." Click on "Advanced" and select "Run as administrator." Click "OK." Place your cursor in the shortcut key, and then press the C key. This sets Ctrl+Alt+C as the shortcut. Click "apply" and say "OK." Now press Ctrl+Alt+C. You'll be prompted and you can either click "Yes" or press Alt+y. Now we have a command prompt in administrator mode.
Out of the box, Site Studio nodeIds are unique across all websites on a WebCenter Content instance. However, there is a configuration flag to change this. If the WebCenter Content configuration flag SSGenerateUniqueNodeIdsis set to 0 (false), nodeIds will only be unique within each website.
Be careful changing the default value for SSGenerateUniqueNodeIds to be false. It is usually assumed that nodeIds are unique across all websites on a server and many times this is the way the code has been written.
WebCenter Content Server will deny a check-in when the primary file and the alternate file both have the same file extension. This default behavior is to discourage users from checking the same file in for both the primary and the secondary. Why might they do that? Perhaps they don’t know what the fields really mean?
The primary file should be the original asset. The secondary or alternate file is also called the web viewable file. Examples of proper pairings might include:
See the official documentation here:
Other configurations you may find handy: