Alert# FileNet P8 Products- Java Binaries Recertification

Note this ‘must know alert’

For details: http://www-01.ibm.com/support/docview.wss?uid=swg21580143&myns=swgimgmt&mynp=OCSSNW2F&mync=E

Spying on your handiwork

You know it makes our self very happy and confident when you came to know about how bike engine will work along with the riding, even it makes us to drive best with efficient fuel & long run maintenance. So the pinpoint is, developer is the one who must be a key role player at the stages; design,architecture,development,administration & maintenance, only then he can turns his phase in to architect.

Below is the article which just bring you inside what the FileNet API would do behind the executions. Explore and make yourself confident / See you next with few more tuning tips.Thanks.

Preview –This article shows three different techniques to see how much data you are putting on the network and holding in your objects in memory when using FileNet P8 APIs. Those two numbers turn out to be incredibly important when it comes to tuning performance in your code. The article looks at network tracing, P8 Content Java™ API logging, and custom class ObjectDumper for dumping out the contents of an object instance. If you understand the description of the ObjectDumper class, you will end up with a better understanding of the P8 Content APIs and their object model.

Go Deep

Gartner Magic Quadrant 2011-Here it Shows!!!

The ECM Magic Quadrant is an analysis of the Enterprise Content Management market done by Gartner. The report has been produced for a number of years and is updated each year to taken into consideration the changes in the Enterprise CMS marketplace.

There are so many types of content management tools available ranging from document, to web, to digital asset, to records – and for each type thousands of vendors who have written their own solution to support local, regional and in some cases global customer bases.

In order to create a distinction between smaller home grown solutions that cater for local or niche markets with niche products, term ‘Enterprise’ evolved to indicate that a vendors product suite targets a broader market or more than one niche type of content management.

Gartner went one stage further and created a set of requirements that a vendor HAS to meet in order to be considered to be an ‘Enterprise CMS Provider’ and produced a graphical representation of the market in the form of a quadrant.

The quadrant started out in 2004 evaluating some 22 vendors who met the criterion – but with the consolidation in the ECM marketplace, this number has been reduced to circa half the original list today. The quadrants from 2004 to current date have been provided on the right so visitors can see how names have disappeared at the same time as suppliers have moved up (and in some cases down) the quadrant over that period.

2011 Magic Quadrant

Happy New Year – 2012

I wish all my blog followers a very happy and propsperous new year.Let’s fuel ourself to handle the new challenges with positive manner …..

DOJO – My Favourite All-In-One WebDevelopment Framework

No doubt, its a huge bonus for me in terms of development. All these days i was quite worried about UI/presentation layer which tweaks my head if i touch this.

As like others languages, one whcih already persists the drag and drop UI development approaches, that makes the developer happy to achieve his good dream practically. Now its the term for Java guys who all want to render configurations less,coding less and satisfactory UI development with simple JS famework called ‘DOJO‘. For the past one month i was being involved to make myself perfect with DOJO, at last i did it. Not a master but gained enough confidence to   grab what i want  from DOJO.

 

Effective Logging-Insurance to Application

One of the coding challenges facing today is lack of useful log messages.Logging is the simplest and most effective tool in a developer’s arena. Our developers do not take the time to think through what and where we should add log messages in our codes.

We tend to use only “error” and “debug” level log messages. We use “debug” messages to help test our codes during development stage. But we add these debug messages on an ad hoc basis. And, our applications usually do not have debug level turned on in production (and we don’t want to). The only other time we log messages is when there is an error or exception. This is partly because traditionally developers are not required to provide operational support for the software they write. They are usually removed from production support by 1 or 2 levels- a support team in the client’s organization and then another in their own organization. With SaaS model, this separation is going away to some extent, but the issue persists. Well thought out log messages can save a lot of time & frustration with debuging production issues.

Here is a set of rules I use when I write codes,

1. Use a good mix of 4 levels of log messages- error, warn, info, and debug.
2. Usually “info” to “debug” ratio is 30%.
3. “Info” is the most important log level from operations perspective, yet the most neglected and misunderstood one. Systems should run at info level. I see it as the “system’s heart beat.” At any point in time, anyone should be able to say how the system is doing by reviewing info messages. The trick is to achieve that using the minimum number of messages with just enough useful information.
4. Use “info” message to trace high level application flow.
5. Use “debug” message to trace detailed level application flow. Never use “system.out” messages.
6. Use “warn” level messages when system can recover from a failure. Also use warn when a user is doing anything unusual, i.e. multiple attempt to login, or trying to access functions that they are not supposed to etc. This is specifically useful in the SaaS systems. “Warn” messages can serve as an early warning signal.
7. Send email when an “error” message is logged. Do not use “error” level if you do not want to receive an email about it.
8. Be vigilant about what data you write out in a log message. Only enough data to help track activities, but never any security sensitive data (in the context of the domain).
9. Add context to the log messages. For example, date & time, line#, class name, method name, session id, user id etc. Logging frameworks available in most languages now-a-days log4j and similar frameworks make it easy to automatically add this context to all messages.
10. Format log messages in a way so that it is easy to plop them into a tool like Excel for easier analysis. Here is an example of a good formatted log message,

Note: Few points gathered from my merely followed sources which i experienced and felt better.Thanks

FileNet Workplace Configuration Files and their Roles

Configuration File	Description
Actions.xml	Defines actions that can be performed on objects accessible through the Workplace application. Actions are available from a context menu on the list views and from a document’s Information page. An administrator can modify existing actions, or, with developer assistance, add new actions. See Customizing Actions on an Object.
bootstrap.properties	Defines Bootstrap values for Workplace. These can be updated through the Bootstrap page in Site Preferences. See Bootstrap Preferences.
ClassFilter.xml	Excludes classes from displaying in the Workplace Add and Checkin wizards. Exclusions are defined on a per object store basis for each object type (document, folder, custom object and so on). See Excluding Classes from User Selection.
ConfigurableLabels.xml	Configures common Workplace UI labels, including system property names. An administrator can customize the default FileNet-provided labels on a per-locale basis, eliminating the need to update resource bundles. See Customizing UI Labels.
containericons.properties	For container types, associates mime types with icons displayed in Workplace. Container icons are mainly displayed on the navigation page in front of the folder path, in the folder list, or any other list that contains a folder icon. See Customizing Icons.
content_redir.properties	Configures redirections to custom or third-party applications based on content object types when the user attempts to open a file from inside Workplace. See content_redir.properties File.
customobjecticons.properties	Associates Workplace UI images to different types of custom objects. By default, there is one image associated with custom objects. An administrator can create any number of custom object types and associate a distinctive image for each type. See Mapping Images to Custom Object Types.
download_redir.properties	Configures redirections for downloads. See download_redir.properties File.
help_map.properties	Maps context-sensitive help files to Workplace Java™ Server Pages (JSP) pages. New HTML Help pages can be hooked into custom-developed Workplace modules. See Using Context-Sensitive Help Features.
icons.properties	For content types, associates mime types with icons displayed in Workplace. See Customizing Icons.
InfoPages.xml	Registers custom Information pages. See Plugging In an Information Page or Properties View.
Integration.xml	Sets up commands for integrating custom applications with Workplace. See the Workplace Application Engine UI Service Guide.
p8controller.xml	Configures the out-of-the-box Web Application Toolkit controller. As a subclass of this base controller, the Workplace controller is also configured with p8controller.xml. See ConfigurableController Preferences.
PagingConfiguration.xml	Configures several paging-related options that appear in the tree view control and in list view presentations. See Configuring Paging.
PolicyProcessors.xml	Registers form processors (document or workflow). To override the default behavior of the out-of-the-box form processors, a developer would implement a new custom processor and register it in PolicyProcessors.xml. See Customizing FileNet P8 eForms Processor Components.
PrimaryViews.xml	Registers primary views in Workplace. Primary views are the links such as Browse, Search, and so on that appear to the left, at the top, and/or bottom of Workplace. An administrator can change the order of the views, hide or show views, and restrict access to views. See Primary Views Preferences. A developer can create a custom primary view and register it in PrimaryViews.xml. See Plugging in a Primary View.
PropertiesPage.xml	Registers custom Property views in Information pages. See Plugging In an Information Page or Properties View.
SimpleSearch.xml	Configures the search option checkboxes in the Simple Search page. See Customizing Workplace Search Options.
SitePreferencesPrimaryViews.xml	Configure the primary views for site preference settings displayed in the Workplace Site Preferences Tool. Administrators can specify primary views for site preference settings, organize views into labeled groups, and provide labels for different locales. In addition, developers can create custom primary views for site preference settings using the Web Application Toolkit, which may also be further configured through the descriptor file. For more information, see Customizing Primary Views for Site Preferences.
SystemPropertiesView.xml	Defines the system properties per object store that will be exposed in the Workplace UI. For various object types, an administrator can select the properties to show in the UI. This file is modified by the Workplace application through the “Object Stores” view of the Site Preferences page. See System Properties View Settings.
WcmApiConfig.properties	Configures the Content Java API. An administrator would modify this file to change the Content Engine that Workplace accesses or the type of credentials protection used. See WcmApiConfig.properties File.
web.xml	Defines low-level configuration settings, servlets, and MIME mappings for Workplace. See Setting Up a New Application: Step 4 – Modify Web.xml. The MIME mappings in the file are used as overrides by the upload handler included in the toolkit. If a user sends a document that has an extension that matches one of the MIME mappings, then its corresponding MIME type is used, regardless of the mime type sent from the browser. Extensions currently defined are .doc, .xls, .ppt and .svg. See Document Upload: Customizing MIME Mappings.