Looking for an Oracle IPM replacement?

You have hundreds of thousands, maybe tens of millions, of documents in your old Oracle IPM 10g system with only 6 months before Oracle closes the support door on that product forever. Or maybe you’re running an Optika Acorde or Stellent IBPM system which has been out of support for years. You’ve looked at the new Oracle 11g platform and it’s too heavy, complex, and missing many key capabilities that you need, features like: external searching with Linked Servers, COLD support, Office and .NET integration points, easy setup and maintenance, and a workflow system that is actually usable for someone without a PhD. Oracle is clearly, and publically, going in a different direction and moving away from traditional enterprise imaging and transactional content management.

And even if you knew of an appropriate replacement technology, how are you going to migrate all of that content out of IPM without disrupting your business? What product vendor is going to know enough about your old IPM system to be able to get the content , applications, saved searches, workflows and profiles moved to their platform? Oh, and you don’t want simply to replacement on product for another – you want a good return on this migration investment!

ImageSource has been delivering and servicing Optika Acorde, Stellent IBPM, and Oracle IPM systems for nearly 20 years (don’t get me started on eMedia!). We recognized Oracle’s change in direction several years ago and have created the perfect replacement solution for the retiring 10g product. The ILINX suite offers the same content management capabilities as IPM but goes way beyond that. In fact, ILINX is more powerful, easier to deploy, use, and maintain, with better scalability, 100% browser-based, built-in retention management, more secure, free mobile clients, cloud-ready, built on the latest Microsoft technologies.. I could go on and on.

Check it out for yourself at www.ilinx.com

Join the dozens of other Oracle IPM customers that have made the easy switch to a better, more powerful ILINX solution!

Randy Weakly
VP of Software Development
ImageSource, Inc.

Windows Phone 8 Features Detail Leaks

If you have not seen the features list, check them out here.  I think the most important items from that list is the tight integration between Windows Phone and Windows, the desktop version.  According to various leaked info this layer will contain the kernel, networking stacks, security model, multi-core processor, and multimedia.

It would be interesting to see how much of it is true later this year.

Windows Presentation Foundation Host Has Encountered a Problem

Every now and then we run across a weird deployment issue where certain XP machines are not able to run ILINX Content Store with the weird exception below

The issue is caused by either an incorrect/corrupted permissions set on the user working folder or the registry key.  The fix is to run the tool below from Microsoft.

Phong Hoang
ImageSource, Inc. 


Dynamically Generating A TableLayoutPanel

The TableLayoutPanel in .NET is a great control for organizing other controls on a Windows form.  We here at ImageSource use it all of the time.  Most developers just generate all of the rows and columns from designer and never mess with the control again at runtime.   Unlike the ListBox and ListView controls,changing the Rows and Columns at runtime is not immediately obvious in the TableLayoutPanel. The following set of code will demonstrate will demonstrate a way to accomplish this non-intuitive task.

Continue reading

Pinning Apps to the Task Bar in Windows 7

In Windows 7, it is possible to “pin” an application to the TaskBar so you can open it with just a single click. To pin something, simply drag the icon to taskbar and click on the “Pin this program to the Taskbar” popup menu item.
I do this with my Visual Studio shortcuts to save time hunting on my desktop or in the Start Programs menu.



Installing Windows 7 on a Netbook?

Below is an awesome tool to use if you are planning on installing Windows 7 on a machine that does not have a DVD drive.  This tool allows you to put Windows 7 on USB drive and run Windows installation from there.

If you got one those netbook with XP on it and the machine has at least 1GB RAM and 1.6 GHz, I would format it and install Windows 7 on it.



How to Report Bugs

Most programmers I’ve worked with are delighted to fix bugs in their code. Yes, really. It’s the social interaction which goes with it which is often the root of the problem. This is always a tricky subject because by definition something isn’t working right when you have to report a bug; you, the user, are frustrated because the software is not working as you expected and you might have very little control over getting the issue resolved.

I came across an old web page this week on how to report bugs. This is written from the programmer’s point of view, and I can say that it’s pretty close. In discussing it internally at my company around the “virtual water cooler,” I was reminded of the occasional travails experienced by our own Tech Support group in supporting our customers and getting us developers the info we need to fix those bugs.

The previously mentioned article talks about how to provide information to the developer to enable them to fully understand (and recreate) the issue. Recreating the issue is paramount so that once it goes away, we know we actually fixed the problem.

My own version of the summary from the article is this:

  • The first aim of a bug report is to let the programmer see the failure with their own eyes. If you can’t be with them to make it fail in front of them, give them detailed step-by-step instructions so that they can make it fail for themselves. After writing down these instructions, go through them yourself to see if they actually produce the results you are describing. At last 50% of the time, the first set of step-by-step instructions are missing something.
  • Don’t make assumptions, be crystal clear in your instructions, if a dialog needs to be dismissed, then note that; if you open something via a menu versus a shortcut key, mention that.
  • Describe everything in detail. State what you saw, and also state what you expected to see.
  • Write down any error messages *exactly* as they appear, spacing and capitalization and all. Hunting down an error message in the code is so much easier when you are looking for the correct string.
  • When your computer does something unexpected, stop. If you start trying to fix the situation, write down each and every thing you do. Many issues are made harder to resolve because someone modified a setting and forgot to mention it.
  • It’s okay to try to diagnose the problem, but in reporting what you think the error is (I think the catalog file is uninitialized when switching contexts), report *why* you think that, providing all the supporting evidence (pro and con) for your conclusion. You may be right, or you may be simply adding confusing information.
  • Be ready to provide extra information if the programmer needs it. If they didn’t need it, they wouldn’t be asking for it. They aren’t being deliberately awkward. Have version numbers at your fingertips, because they will probably be needed.
  • Be proud. You are engaged in a process to improve the world, or at least the small corner in which you live, or making your software work a little bit better.

It seems to be that there are some basic categories of bugs:

  • Coding error in the software, an actual bug (2 + 2 comes up as 5 on your calculator)
  • User error (I closed without saving, where’s my work?)
  • Interaction with other software (this new Windows patch broke my website)
  • Misuse of the product (I want to use a spreadsheet program as a word processor)

What else?

(The original article can be found here)

Martin O. Waldron
Program Manager, SW Development
ImageSource, Inc.