Archive for the ‘Collaboration Server’ Category
Sunday, February 27th, 2011
Last month, we wrote to tell you about the WebCenter Interaction Collaboration Server IE8 Critical Fix. Last week, an old Plumtree pal dropped me a line to let me know that this patch has been updated (Thanks, Eno!). No new version information – it’s actually the exact same patch number and everything – although some of the code has changed a bit. As far as I can tell in analyzing the different packages, there are just a couple of tiny tweaks, and the release notes include a more comprehensive set of bug fixes, so you’ll just have to download the patch again to get the new binaries.
- WebEdit does not work on IE8. (9723488)
- Error in task submenu in IE8 (9712774)
- Cannot upload multiple files in Collab (9274372)
- Bulk upload JRE updated to 1.6 in order to support IE8 (8760280)
- Notifications should be sent from a fixed address for creation and deletion (9647426) This fix involves updates to both collab and notification components.
- Subscription to project overview causes conflicts with Immedate Subscriptions (8759642)
- Non gatewayed webedit does not work (9434805)
- File leak in Search Service during search index rebuild (11726008)
- Webcenter Collaboration notifications to large numbers of recipients fail (9484113)
Oh, and while I never got around to writing a post about this, for those of you that are into this kind of stuff, this update includes a new cns.war file – and someone in engineering has removed the .jars containing some of the CNS source code. So if you want to take a peek, check out the code in your cns.war before updating.
Guess you’ll have to find some other way to meet your code analysis needs…
Tags: Collaboration, Critical Fix
Posted in Collaboration Server, Oracle | Comments Off
Monday, February 7th, 2011
When working on self-signing the Plumtree Collaboration WebEdit applet to prevent the certificate warning, I had to install WCI Collaboration Server 10.3.0.1 on my server. As I usually do, I made a backup of the collab folder, ran the install, and used Beyond Compare to diff the results. Interestingly, I found this little gem in the collab.war file in /docman/editor/officeToolsInstall.jsp:
Wha-? Why would 10.3 have a cookie expire on 1/1/2020, and 10.3.0.1 have the same cookie expire on 1/1/2010? Who knows, but what it likely means is that te “Do not show this again” checkbox in the Collaboration Office Tools popup will never work, because it’s setting a cookie that’s perpetually expired.
The solution? Install that Collaboration Server IE8 Critical Fix, or just crack open the .war file and update /docman/editor/officeToolsInstall.jsp to use 2020 for the cookie expiration date.
Tags: Collaboration, cookie, javascript
Posted in Coding Tricks, Collaboration Server | Comments Off
Thursday, February 3rd, 2011
While this blog isn’t the de-facto source for Oracle WebCenter Interaction critical fixes, we’ve tracked a big chunk of the latest hotfixes - including the more recent Analytics update and Collaboration Critical Fix for IE8.
I’ve done a couple of installs with this Collaboration IE8 fix, and although I still haven’t seen Bulk Upload or WebEdit really get bullet-proof (frankly, WebEdit in particular is the bane of my existence), one thing is certain with these updates: Oracle updated the code-signing certificate for the Bulk Upload applet in the latest critical fix, but never bothered updating the WebEdit applet.
What does this mean? Well, when you’re uploading files with the Bulk Upload applet, you get a message that the certificate has been validated by a trusted source:
But, whenever you load a page with Collaboration portlets on it, the WebEditControl applet loads (more on this another time), and you get a signature warning that says “The digital signature was generated with a trusted certificate but has expired”:
Oracle’s official stance can be summarized thusly: “Pfft, what’s the big deal, anyway? Suck it up or fix it yourself.”. OK, so while I took some liberties with my paraphrasing there (sorry Oracle!), I went with option two: self-signing the WebEditControl applet. It’s a non-trivial exercise, and all you get out of the deal is a nice clean prompt without the warning, but I’ve heard enough inquiries about this warning so I figured I’d just fix it:
The best part for you? You can save yourself the huge pain of getting a code-signing cert, and download the Integryst-signed .jar file after the break, and say goodbye to that signature warning! (more…)
Tags: Certificate Warning, code-signing, Collaboration
Posted in Collaboration Server, Integryst | 3 Comments »
Friday, January 14th, 2011
Now that Internet Explorer 9 is (almost) out, Oracle has gone and thrown us a new update to WCI Collaboration Server to finally support IE8. Well, to be fair, this was released last October.
The patch does have some mixed messaging about what “officially supporting” means:
From the release notes: “The application of this patch updates Collaboration 10.3.0.1 to officially support Internet Explorer 8.“.
From the Oracle Support Site, though: “Not every issue that has been identified when using IE8 with Oracle WebCenter Collaboration has necessarily been addressed by this patch. A specific set of defects discovered in testing and resulting from customer feature requests were deemed the “essential” fixes required to establish a baseline of support for the browser version.
If you experience issues other than those resolved by the patch, the fact that IE8 is now “Fully Supported” once the patch is implemented means that you can log an SR with support who can than verify the defect and log an appropriate bug tracking ID. ”
It does have some pretty decent fixes, here, though, and I recommend this patch – I did some source analysis on the new version and did find quite a few changes in this new build – particularly around the Bulk Upload functionality:
The patch can be downloaded here; A copy of the Release Notes is after the break for your convenience…
(more…)
Tags: Collaboration, Critical Fix
Posted in Collaboration Server | Comments Off
Thursday, September 16th, 2010
Generally, my Cool Tools articles feature tools that are novel, unique, or otherwise helpful when managing WebCenter Interaction portals, or other applications that can help augment (or – dare I say, replace?) it. Today’s Cool Tool is in a category where apps are a dime a dozen. So, let’s call, uh, Webnet77.com’s Base64 Decoder a Cool Tool:
Why highlight a dime-a-dozen online app that’s pretty much just a free online tool? Because today I’m going to explain a bit about how Basic Authentication works between the portal and remote tier, and show you a trick to answer a question that you may have come across during your portal administration: what password has been configured for the “authenticationid” in the portal for ALUI Publisher Remote Server (or Collaboration Server, for that matter)? In the process (after the break), hopefully you’ll get a little insight into why it’s not all that secure in and of itself. (more…)
Tags: Base64 decoder, Cool Tools, tricks
Posted in Collaboration Server, Cool Tools, Publisher | 1 Comment »
Thursday, August 5th, 2010
The IDK methods for Collaboration Server are terribly sparse – you can’t get calendar events, file sizes, or a whole bunch of other critical data that you may want if you were to actually embark on a mission to write a better UI for Collab (trust me, I have). Sure you could try and use the woefully undocumented Collab API – I’ve shown you how to deploy the portal API in the past – but that’s a challenge in and of itself.
Instead, let’s look at an alternate approach: use the Collab Server as a sort of REST API. It’s not really, but the basic idea is that you use URLs in your code to directly call functionality in Collaboration Server to do certain tasks. For example, say you want to add a Collaboration project to a page programmatically; there is no mechanism to do this through the IDK, and we have no idea how to use the API, but using a header tool, we find that through Project Explorer, it works with a simple URL: /collab/do/project/selector/add?commPage=true&projID=COLLABID.
So, it turns out we can do the same thing programmatically, by using Java’s network libraries to call that URL directly (setting the proper authenticationid). The code after the jump shows an example of how to do this; we use this approach in Integryst’s Automater, which allows you to script a bunch of actions at a time (what good is automatically creating a collab project if you can’t add it to a community page you just created!?).
Tweak away!
(more…)
Tags: Code Samples, Collaboration, hack
Posted in Coding Tricks, Collaboration Server | 1 Comment »
Friday, July 9th, 2010
The Plumtree Server stack has had a long history, forming a decent patchwork of usable applications, but never quite getting to the point where every part of the stack is consistently configured. When it became ALUI (AquaLogic User Interaction), there was a movement towards putting configuration settings in one place – the Configuration Manager – but unfortunately now that Oracle is holding the reins and the future of the stack is in question, it looks like we’ll never have that utopian vision of single, centralized way of configuring all applications the same way.
Case in point: configuring the memory parameters for Collaboration Server. While Publisher utilizes a config file for memory settings, Collaboration Server passes memory parameters via the service startup path. So, if you’ve got a decently large Collaboration install, you might find that you’re running relatively low on memory:
To up the amount of RAM available to Collaboration Server, you need to edit the registry (and yeah, back it up first!). The key you need to change is in HKLM\ SYSTEM\ CurrentControlSet\ Services\ ptcollaborationserver, and it’s called “ImagePath”:
Change the “-Xmx” value to something larger, restart Collab, and you’ll have more RAM breathing room:
Tags: best practices, Collaboration, java, memory
Posted in Best Practice, Collaboration Server | Comments Off
|
