Liferay Portal is not a deep space transmutation Device! It is a framework to create websites, Content Management Systems (CMS) and intranet applications. The Liferay Portal can simplify the work and user experience, and is easily customized to cater to specific preferences and needs. Liferay works with all operating systems, databases and application servers and it has over seventy (70) tools to help you customize and set-up your portal, content, collaborative process, etc. But, as my friend, Debbie recently learned, you definitely want to find the right partner to help you get the most out of Liferay and navigate the space/time continuum so you can get where you want to go. My friend Debbie works for a media company and her IT team selected Liferay Portal to manage content, which was a great choice. What wasn't such a great choice was trying to use the internal team to manage the design, development and implementation. But, let's not talk about Debbie's sad story.###Details >
Invest $1 and get a $100 return? Sure where do I sign? So, what are you waiting for? That’s what Ux design/re-design can do for YOUR business.
Tally ERP provides small to medium sized (SME) businesses with an accounting and inventory management solution. This solution is very popular among SMEs on the Indian subcontinent, in the Middle East, Far East, and Africa and other countries around the world. It is affordable, and easy to use for accounting and inventory management. Tally is a popular solution for small to medium sized companies in all types of industries. In Parts I thru IV of this article series, we discussed the need for expanding SMEs to consider an integrated Business Intelligence Solution that will provide more comprehensive, sophisticated, personalized and mobile views and analysis of integrated data from Tally ERP and other enterprise solutions. Parts I thru IV of this article series focused on reporting capabilities, integrated data compilation and analysis, mobile, secured access to data, and data mining and user personalization. Part V of this five part article series focuses on the importance and benefits of a self-serve business intelligence environment that will allow Tally ERP users to continue to leverage this solution as well as other technology investments.###Details >
Elegant MicroWeb has announced the launch of a major version of its flagship Business Intelligence Suite, ElegantJ BI. Version 4.0 is set to transform the way Business Intelligence Solutions are used and deployed. The new version has a fresh, redesigned user interface and offers intuitive user experience across desktops, laptops, mobiles, and tablets regardless of the client device platform. ElegantJ BI Version 4.0 with a new interface will make using the product a real delight, whether you are designing a dashboard or doing deep dive analysis. Utilizing the latest technology, ElegantJ BI is 100% browser based and does not need any native apps or plugins. Using responsive technology, the interface will let you have the complete power of Business Intelligence on a laptop, a tablet, or on your smartphone, as each dashboard, graph, KPI, or analysis will resize and render itself optimally based on the shape and size of the target device.###Details >
Are you ready to give up your mobile customers? If NOT, you’d better embrace Responsive Web Design, if you want to keep and hold your customer’s attention.
Now that WordPress version 4.0 has been out in the market for a while, users, developers and the media have had some time to look at the new version and comment on the changes, new features and improvements. There is a lot to like about the new version of WordPress and, much to like if you are a developer who designs and executes projects for small and medium sized businesses. As WordPress continues its evolution, it has gone beyond appealing to bloggers and sole proprietors and reached for a market that includes businesses looking to use this framework for content management and/or sales and marketing of products and services.###Details >
The business intelligence software market is growing rapidly around the world, and with good reason. Business owners and managers are well aware of the importance of fact-driven, performance-driven business decisions and results. But, there is one thing that many businesses overlook when they are considering and selecting BI tools, namely, the importance of business intelligence democratization. If a business is to be successful, it must engage and align its employees with the strategic, operational and tactical goals of the enterprise and link empowerment and accountability to these goals.###Details >
In software programming, the use of frameworks makes things easy and saves a great deal of time for developers. In the Java world, Spring Security is one such framework that is worth consideration by developers. Spring Security is part of the larger Spring Projects Umbrella, and the framework can be used to implement security aspects in Java web applications. Spring Security makes a developer's job easier and ensures that an application is secure by configuring the appropriate elements in the xml file. It also provides support classes and various filters, as well as support for custom requirements. It is worth nothing that Spring Security sometimes requires a bit more work to achieve specific, complex requirements, but the tool is, nevertheless, a worthwhile addition to any developer's toolkit.One of the common requirements in web development is to gracefully exit from the application when a user session expires. In this article, we will look at how Spring Security can help a developer to easily configure and handle a session timeout, and explore the issues and workarounds that you'll need to understand in order to successfully utilize the tool. Configuration The following explanation assumes that the reader understands the required configuration xml file needed to implement Spring Security, is the xml element where we need to make changes. To tell Spring to show a separate page when the user session has expired, you can simply specify the URL value in the invalid-session-url attribute - and then, you are done! When the user tries to make a request after being idle for some time, and session has already timed out, Spring will direct the user to the specified page. Problem This configuration is very simple. But, it will create one problem. Even when a user logs out properly from the system, he or she will get the session expiration page instead of the login page (we'll assume here that you have setup the login the URL as a logout-success-url in element). This problem occurs because, when user logs out, Spring invalidates the user session. On the next request to show the login page, the browser will send the cached session ID to the server. But, since the session associated with the given ID is invalidated, Spring will redirect the user to the session expiration page as configured. Workaround 1 One workaround to this problem is to tell Spring not to invalidate the session on logout event. This can be done by setting the value of invalidate-session attribute to “false” in element. This configuration will keep the user session alive on the logout event, so the user will be redirected to the login page, rather than to the session expiration page. But you may not always be able to keep the session alive when the user logs out from the application. In that case, use Workaround 2. Workaround 2 The other workaround is to delete the session cookie on the logout event. You can do so by using delete-cookies attribute of element. As you can see, we asked Spring to delete the cookie named “JSESSIONID” on the logout event. Because the browser will not send any session ID on the next request, Spring will direct the user to the login page, and thereby solve the problem. This approach may work for some containers but not for others. For instance, if you are using Apache Tomcat version 7, this workaround will not succeed. In this case, Spring won't remove the cookie in spite of the delete-cookies attribute value that is specified, because it can’t find the matched cookie path. When Tomcat sends the cookie to the browser, it appends the extra slash (“/”) to the end of the context path, e.g., path = “/foo/”. Tomcat has a good reason to do this because IE gets confused in sending cookies to the server for matching domains. For example, it will send the cookie meant for “/foo” to the domain “/foobar” as well. Please note that this behavior has been noted by other developers, but we have not personally verified this. To solve this problem, Tomcat appends a slash at the end of the context path. Now, when you set the delete-cookie attribute, Spring tries to find the cookie for the path without a slash at the end. Because it doesn’t find it, the cookie will not be removed, resulting in the display of session expiration page instead of login page. Luckily, Spring provides the flexibility to make custom changes in the default behavior. To solve the above problem, you need to write your own logout handler to remove the desired cookies. For that, we will need to use a “logout filter” instead of “” element (i.e. remove the entirely from the configuration file).###Details >