Monthly Archives: December 2013

  • 0

Future of Enterprise Content Management: Hybrid ECM

Tags : 

The rise of cloud computing, social networking and mobile usages is considerably changing the way people work; this has major implications for the management of enterprise content.

People want to share information easily with collaborators, and they want to access their content anytime, anywhere, and using any device.

While delivering content to range of devices, organizations need to ensure users for the security of their content.

Some questions has been posted to Melissa Webster, vice president of IDC’s Content and Digital Media Technologies research by Alfresco and here is what Melisa feel about Hybrid ECM for the coming years.

In order to be more productive people are demanding to use mobile devices to get their work done.  As per IDC research more than 65% information workers are expecting to use tablets or smart phones for work purposes. They want each feature to be available to the mobile app which they do with their laptop computers, including viewing and editing of the document, sharing of the document, assigning tasks to the users etc. Major challenge for users to work offline with the content while they are not connected to network, smart phones and tablets are the key and convenient platforms for users to work with enterprise content in offline mode.

Cloud solutions are evolving at a very high rapid race. Prefer a vendor that fosters strong environment for enterprise solutions and as user you should be benefited from all the innovations. There is variety of vendors which provide services that includes collaboration with users, rights management, smart phone device management this leverage their customers use of the innovation era.

According to IDC hybrid ECM is the right model for Enterprise solutions. It’s the solution for mixed deployment environments. ECM is tightly coupled to the applications that consume enterprise content. It’s difficult to move ECM to the cloud when those applications continue to run behind the firewall. A hybrid ECM solution lets customers move the content that can be moved to the cloud. Hybrid ECM is the right solution for cloud based applications such that mobile users can enhance collaboration without disturbing existing production applications.

Keep Following for more Technology and Enterprise news.

  • 0

Java: Stories 2013

Tags : 

2013 was a year of Java releases. The JavaOne 2013 opening video is available on YouTube/Java channel now. It is a great story of how Java is improving our lives, and how the world is getting connected. Following are some of the top stories of Java in the year of 2013:

Release of Java EE 7

Java Platform, Enterprise Edition 7 (Java EE 7) offers new features that enhance HTML5 support, increase developer productivity, and further improves how enterprise demands can be met. Java EE 7 developers will write less boilerplate code, have better support for the latest Web applications and frameworks, and gain access to enhanced scalability and richer, simpler functionality. Enterprises will benefit from new features that enable portable batch processing and improved scalability.

JavaFX is Open Source

In January, first code drop of JavaFX 2.0 source code was made public on OpenJFX. Everybody is welcome to contribute to this project, port it to other platforms or devices, or do anything else that a free software license allows you to do!

Java and the Internet of Things

Everyone was waking up to the Internet of Things (IoT) in 2013. The Java language and platform were ready for this new wave. Oracle delivers a comprehensive platform for the entire IoT architecture across all vertical markets. From the Java platform to embedded data-management systems; from back-end databases, big data technologies, middleware, and integration and analytics technologies to extreme performance hardware that turns data into insight, Oracle is the only company that delivers an integrated, reliable, and secure platform to meet your IoT program needs today and into the future.

Java SE Update Releases

Oracle focused and addressed several security issues with Java SE Updates throughout the year: Java SE 7 Update 11 and Java 7 Update 25. Java SE 7 Update 21 introduced new security features, including a Server Java Runtime Environment (Server JRE). Java SE 7 Update 40 included Java Mission Control, set of tools to monitor, manage, profile, and eliminate memory leaks in your Java applications.

Oracle Ends Commercial Support of GlassFish

Oracle announced it will no longer release future major releases of Oracle GlassFish Server with commercial support.

Java attacks reach critical mass

This was a rough year for Java in the browser. Major new vulnerabilities repeatedly battered Java browser plugins, encouraging many organizations to get rid of Java in the browser if possible. But the good thing is, as Oracle had promised, it released an out-of-band fix more rapidly than some observers had expected.

Java SE 8 

Java 8 is expected in March 2014, and will include features that were planned for Java 7 but later deferred. Java SE 8 is well underway, and early access builds are available. Lambdas are a key feature.

Stay tuned for much more about this release in 2014.

  • 0

How to Publish iOS Application to Apple Store?

Tags : 

Before we go ahead, make sure you have following information:

  • Register for iOS developer programe
  • Apple ID having access to Provisioning portal and iTunes Connect
  • 5 Screenshot of Application (Minimum 1)
  • iPhone 4s – 640 x 960 (png format, 72dpi)
  • iPhone 5 – 640 x 1536 (png format, 72dpi)
  • iPad 2 – 768 x 1024 (png format, 72dpi) [this requires if Application support only iPad 2]
  • iPad 3 – 1536 x 2048 (png format, 72dpi)


Step 1: Geting started

Log into iTunes Account and Go to “Manage Your Applications”. Now click “Add New App”.



Enter your Company name: (One Time Step)
If you are creating first application from particular Apple Account then only this screen will come up. (Double check the name, because this is going to same for all the App which is going to publish using this account, also this cannot be changed)



Step 2: App Information
  • Default language: The primary language you will be using to enter app details for display on the App Store.
  • App Name: The name of your app as it will appear on the App Store. Note that this name cannot be longer than 255 bytes.
  • SKU Number: A unique ID for your app. You can use letters, numbers, hyphens, periods, and underscores. The SKU cannot start with a hyphen, period, or underscore.
  • Bundle ID: An identifier used by iOS and Mac OS X to recognize any future updates to your app. Your Bundle ID must be registered with Apple and unique to your app. Bundle IDs are app-type specific (either iOS or Mac OS X). The same Bundle ID cannot be used for both iOS and Mac OS X apps.




Step 3: Pricing and Availability of App
  • Availability Date: The date your app will become available on the App Store.
  • Price Tire: The level that determines both the customer price as well as your proceeds (which is the net price after taxes, where applicable, have been taken out), If your app is free, select Free. If you are charging for your app, you must have a paid commercial agreement in place before you can sell in your chosen tier. (Click on View Price Matrix to know more about Pricing.)
    • Discount for Educational Institutions: Check this box if you want this app to be offered at a discount to educational institutions when they purchase multiple copies at once. The details of the discount are found in the latest Paid Application Agreement, which you must sign before this app will be available to education customers.



Step 4: Version Information

  • Version Number : The version number of the app you are adding. Numbering should follow typical software versioning conventions (for example, 1.0 or 1.0.1 or 1.1).
  • Copyrights : The name of the person or entity that owns the exclusive rights to the app, preceded by the year the rights were obtained (for example, “2008 Acme Inc.”).
  • Primary Category : The category that best describes the app you are adding.
  • Secondary Category (optional) : An additional category that further describes the app you are adding.
  • Review Notes : Additional information about your app and/or your In-App Purchases that may assist our review, such as the details of any test accounts that we can use to test them (including user names, passwords, access codes, etc.) Review Notes cannot be longer than 4000 bytes.


Step 5: Rating
For each content description, choose the level of frequency that best describes yo


Step 6: Metadata 
  • Description : A description of the app you are adding, detailing features and functionality. Descriptions cannot be longer than 4000 characters.
  • Keywords : One or more keywords that describe the app you are adding. When users search the App Store, the terms they enter are matched with keywords to return more accurate results. Separate multiple keywords with commas. Keywords cannot be edited once your binary is in review and cannot be longer than 100 bytes.
  • Support Email Address : An email address where we can contact you if there are problems with your app. This address will not be seen by customers.
  • Support URL : A URL that provides support for the app you are adding. This will be visible to customers on the App Store.
  • Marketing URL (Optional) : A URL with information about the app you are adding. If provided, this will be visible to customers on the App Store.
  • Privacy Policy URL (Optional) : A URL that links to your company’s privacy policy. Privacy policies are recommended for all apps collecting user or device related data, and required for apps that offer auto-renewable or free subscriptions, or as otherwise required by law.



Step 7: Uploads 

  • Large App Icon: A large version of your app icon that will be used on the App Store. It must be at least 72 DPI, in the RGB color space, and 1024 x 1024 pixels (it cannot be scaled up). The file type must be .jpeg, .jpg, .tif, .tiff, or .png. It must be flat artwork without rounded corners.
  • iPhone and iPod touch Screenshots: iPhone and iPod touch Screenshots must be .jpeg, .jpg, .tif, .tiff, or .png file that is 960×640, 960×600, 640×960 or 640×920 pixels, at least 72 DPI, and in the RGB color space.
  • iPhone 5 and iPod touch(5th Generation) Screenshots: iPhone 5 and iPod touch (5th gen) Screenshots must be .jpeg, .jpg, .tif, .tiff, or .png file that is 1136×640, 1136×600, 640×1136 or 640×1096 pixels, at least 72 DPI, and in the RGB color space.
  • iPad Screenshots: iPad Screenshots must be .jpeg, .jpg, .tif, .tiff, or .png file that is 1024×768, 1024×748, 768×1024, 768×1004, 2048×1536, 2048×1496, 1536×2048 or 1536×2008 pixels, at least 72 DPI, and in the RGB color space.
  • Routing App Coverage File (Optional): Routing app coverage files are .geojson files which specify the geographic regions supported by your app. The file can have only one MultiPolygon element. MultiPolygon elements consist of at least one Polygon. Polygons contain at least four coordinate points. Polygon start and end coordinate points must be the same.


Step 8: Manage In-App Purchase (Optional step, if application does not contains any In-App Purchase)
Click on “Manage In-App Purchases”


and Click On “Create New”.


Select In-App Type


In-App Purchase Summary
  • Reference Name : The reference name will be displayed in iTunes Connect and in sales and trends reports. It will not be displayed on the App Store. The reference name cannot be longer than 255 bytes.
  • Product ID : A unique identifier that will be used for reporting. It can be composed of letters and numbers.


Pricing and Availability:
  • Price Tier : The retail price for this In-App Purchase subscription. (Click on View Price Matrix to know more about pricing)


In-App Purchase Details

  • Language : Details for this In-App Purchase are shown below. You must provide at least one language at all times.


Hosting Content with Apple: Select if you want Apple to host your In-App Purchase content. If you select yes, you must upload your content to Apple before sending the In-App Purchase for review.
Review Notes (Optional): Additional information about your In-App Purchase that can help us with our review, such as test accounts that can be used (including user names, passwords and so on). Review notes cannot exceed 4000 bytes.


Screenshot for Review: Before you submit your In-App Purchase for review, you must upload a screenshot. This screenshot will be for review purposes only. It will not be displayed on the App Store. Screenshots must be at least 640×920 pixels and at least 72 DPI.


Step 9: Bind In-App Purchase to Application (ignore if your application does not have In-App Purchases)
Click “View Details” from current version of Application.

Screen Shot 2012-09-25 at 3.14.43 PM

Go to In-App Purchase section to select In-App Purchases.
Screen Shot 2012-09-25 at 3.03.05 PM
Step 10: Ready Upload Binary

Once you are done with all above steps, Double check all the information before you change state of Application. Click on “Ready to Upload Binary”Screen Shot 2012-09-25 at 3.12.13 PM

Now, Go back to App Summary page, You can see that your Application state is changed to “Waiting For Upload”

Screen Shot 2012-09-25 at 3.14.43 PM_0

Step 11: Upload Binary
There are two ways to upload binary to iTunes.
1. Using Application Loader (Recommended, because you can have watch on each activity of upload)
2. Using xCode.
Read this Article to know How to Upload Binary to App Store
Once you upload your binary to iTunes, Your Application status changed to “Upload Received” and automatically state will change to “Waiting for Review”.
So, Now your Application is under Apple’s reviewal process. Once your Application is reviewed by apple Apple get back to you with approval or rejection with proper reason.
All the best for Apple Reviewal Process !!
Thanks for reading the Article.


  • 0

Send an email from liferay portal

Tags : 

If you want to send an email from your liferay portal then its bit easy because liferay provide an Utility class called MailEngine.So we don’t have to play with direct JavaMail API.

In this article, we’ll use Gmail as SMTP

Below are the steps to send an email in Liferay.

  • Configure your SMTP provider, outgoing port, user id and password.
  • Login as super user in your liferay portal
  • Go to Control Panel
  • Click on Server Administration from server section
  • Click on Mail Tab
  • Fill out the SMTP fields here,
  • Set Outgoing SMTP Server (E.g.
  • Set Outgoing Port (E.g. 465)
  • Check the box of Use a Secure Network Connection if you want.
  • Set User Name and Password.
  • Press “Save” Button
  • You are done with SMTP configuration of outgoing mail sever.
  • In your MVCPortlet or related class add the below peace of code to send an email.
    MailMessage mailMessage = new MailMessage();
    mailMessage.setBody("set body here");
    mailMessage.setFrom(new InternetAddress("fromAddress","fromName"));
    mailMessage.setSubject("set mail subject here");
    mailMessage.setTo(new InternetAddress("set receiver email id here"));
  • If you want to add attachment to your email or you want to add Cc you can use below send method of MailEngine class,
    send(InternetAddress from, InternetAddress[] to, InternetAddress[] cc, InternetAddress[] bcc,
    String subject, String body, boolean html format, InternetAddress[] replyTo, String messageId,
    String inReplyTo, File[] attachments);
    I hope this tutorial will help you.. :)

  • 0

New Expected Features in Drupal 8

Tags : 

This post introduces some new features in Drupal 8 content management like Inline Editing and UUIDs.

About Drupal

Drupal is a free and open-source content management framework (CMF) written in PHP and distributed under the GNU General Public License. It is used as a back-end system for at least 2.1% of all websites worldwide ranging from personal blogs to corporate, political, and government sites including and It is also used for knowledge management and business collaboration.

New Features in Drupal 8:

[A]. Universal Unique IDs (UUIDs)

Drupal 8 will also add more uniformity to data structures.  In previous versions of drupal you’d have IDs for nodequeue, taxonomy terms, and many other units of content.  With universal unique IDs (UUIDs) assigned to multiple types of content, development will be more streamlined, particularly during migrations.

[B]. Web Services and Context Core Initiative (Whiskey)

Typically, a site receives an HTTP request from a user browser and then returns HTML; however, there are cases where data must be sent and received between sites.  In Drupal 8, Drupal will become a “Restful” interface, with the following attributes:

  • Machine to machine communication – A common use-case for this is sharing feeds between Drupal Sites.
  • Stateless – There is no need to define a context for the data.  Data is requested the same way each time.
  • Multiple HTTP methods are used depending on the activity – POST for creating, PUT for updating, GET for requesting data, and DELETE for removing it.
  • Caching – Frequently requested data can be cacheable for efficiency and scalability.

[C]. Views in Core

Another great feature of D8 is Views in Drupal Core. This and a great and long-awaited change. This simplifies things when clients need to customize things like the content list page.  Instead of making a fresh view or modifying it a more invasive way, developers can simply modify the view.

[D]. Configuration Management 

With the Configuration Management Initiative, Developers will be able to take a snapshot of overall Drupal configuration at a specific point in time. This will be an invaluable tool, similar to featurization, that will help streamline development, deployments, and migrations. When a setting is changed it will be saved in a config file as well as the DB. Allowing configuration to live in the file system This allows changes to be deployed via version control.

[E]. Theming and Presentation Changes

Drupal’s mobile support is improved with the Mobile Initiative.  With the growing popularity of mobile devices it is essential for Drupal to improve its support of this medium. To this end, the default Stark, Bartik, and Seven themes are expected to become responsive, meaning that their presentation changes based on the browser width.

[F]. Improved Content Authoring Experience

Using the Spark project, D8 will support inline editing.  This will allow content updates directly on the page via AJAX rather than the traditional edit form workflow.  Furthermore, the Media module is expected to be moved to core which should make image and video development easier. Note that the conventional “edit page” workflow will still be possible.

Keep following us for more details of Drupal versions.