Prolifics' AJ Aronoff on Healthcare Infrastructure Demands

AJ Aronoff is a Practice Director and IBM Champion covering Application Infrastructure at Prolifics. Recently at IBM Impact, AJ was interviewed on current infrastructure demands in the healthcare industry. Specializing in solutions for the healthcare industry, AJ explains how he can help the industry understand the latest healthcare regulations. In this video, he discusses the value that IBM WebSphere Application Server (WAS) brings to the industry, and the latest advancements in WAS 8.5. In addition, AJ explains the impact mobile technology is having on the healthcare space, opening up the possibility to cut down on a lot of the paperwork as well as allowing doctors and medical staff to record information at each bedside.

View AJ's interview on Healthcare Infrastructure Demands!


Interested in learning more? Contact AJ Aronoff today - aj@prolifics.com.

To learn more about Prolifics, visit www.prolifics.com.

AJ Aronoff is the Application Infrastructure Practice Director for Prolifics and an IBM Champion for IBM WebSphere. AJ first joined Prolifics as a Developer, then specialized in WebSphere MQ. He has 25 years experience in the IT field — 17 of those years at Prolifics. As a Prolifics consultant, he has done MQ design, implementation, infrastructure, monitoring and security assignments at several large financial, insurance, retail and communication firms (Bloomberg, Credit Suisse, Deutsche Bank, DTCC, Fidelity, ITG, JPMC, Och Zif, Tokyo Marine, Pep Boys and British Telecom). He has presented on security and infrastructure at Impact, Hursley comes to Minneapolis and Palisades, and MQ User Groups. His customers use Omegamon to monitor over a thousand systems across the globe.

Application Performance Testing Best Practices

Application Scalability:

1. Define Application Scalability in two ways:    a. Vertical         b. Horizontal
2. Vertical scalability is defined as the scalability of an application as additional CPUs are added to the same server
3. Horizontal scalability is defined as the scalability of an application as additional servers are added to the environment
4. Scalability of an application is important for large enterprise Portal deployments where an individual server cannot support the anticipated load. In such cases, the Portal provides the capability to cluster multiple instances of the application. This can be achieved by either installing multiple instances of the Portal on a single server with a large number of CPUs or having each instance run in a separate Java Virtual Machine (JVM), a combination of both
5. Performance improvements are depends an operating system, application server and JVM handle the scheduling of threads across a larger number of CPUs. This is also subject to change as subsequent versions of JVMs are released to market. In addition, careful tuning of the application server is required to ensure that the load on a single instance can be most effectively supported (e.g., Web Sphere Web Container Thread Pool parameters)
6. For horizontal scalability, the only limitation on the scalability of the Portal will most likely be from the network or database perspective (the database is a shared resource between all instances of the Portal in a particular cluster). Any other system component that is shared by all Portal instances (e.g., LDAP Directory server) can potentially create a bottleneck and prevent further scaling of the application.
7. Portal instances running in a clustered environment it is required Portal network throughput is below 70% of the maximum network bandwidth available at peak periods (i.e. maximum of 8 MB/sec on a 100 Mb/sec network). Network throughput levels above this will impact the average response times for end users during these periods.
8. Database CPU utilization of above 75% at peak periods can greatly impact the Portal performance depending on the types of queries being executed at that time

Web Server:

1. If a web server (e.g., Apache, Sun ONE, IIS) is using proxy to accept request from the application server in a production environment, it is recommended to host the web server on a separate physical server. Such a configuration may be encountered in an Internet deployment with a DMZ (Demilitarized Zone)
2. The net effect of this is that more resources, in the form of memory and CPU, will be available to the application server to process requests. This will have a small impact on the response times due to an additional network hop but will increase the overall throughput of the application due to the additional CPU resources that will be available

Application Server:
Tuning parameters for Web Sphere & Apache Tomcat application servers
WebSphere:

1. The optimal number for the Web Container Thread Pool Maximum Size is 75 (default is 50). Both lower and higher values result in slightly lower throughput.
2. Increasing Thread Pool Minimum Size has adverse effect on performance.
3. Similarly, increasing Thread Inactivity Timeout has a slightly negative effect on performance.
4. Running Performance Monitoring Service introduces about 30% overhead

Apache Tomcat:
The development time issues relate to how the Java code for the Web application was designed and implemented. Again, there is a whole set of implementation best practices surrounding this area, such as:

1. Do not create sessions for JSPs if they are not required
2. Do not store large objects in your session.
3. Time out sessions quickly, and invalidate your sessions when you are done with them.
4. Use the right scope for objects.
5. Use connection pooling for improving performance.
6. Cache static data.
7. Use transfer objects to minimize calls to remote services.
8. Minimize logging from Web applications, or use simple logging formats

Database Server:
For large enterprise deployments of the Portal, it is recommended that a dedicated database server be used to host the Portal schema. In addition, certain database subsystems (e.g., MetaStore, Users) can be further distributed across several database servers. Deploying the Portal schema in this manner will help to ensure that the database will not become a bottleneck as the Portal is scaled to support a continually growing user base
Oracle 11g:
To assist in the rollout, build a list of tasks that increase the chance of optimal performance in production and enable rapid debugging of the application. Do the following:

1. When you create the control file for the production database, allow for growth by setting MAXINSTANCES, MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, and MAXLOGHISTORY to values higher than what you anticipate for the rollout. This technique results in more disk space usage and larger control files, but saves time later should these need extension in an emergency
2. Set block size to the value used to develop the application. Export the schema statistics from the development or test environment to the production database if the testing was done on representative data volumes and the current SQL execution plans are correct
3. Set the minimal number of initialization parameters. Ideally, most other parameters should be left at default. If there is more tuning to perform, then this appears when the system is under load
4. Be prepared to manage block contention by setting storage options of database objects. Tables and indexes that experience high INSERT/UPDATE/DELETE rates should be created with automatic segment space management. To avoid contention of rollback segments, use automatic undo management
5. All SQL statements should be verified to be optimal and their resource usage understood
6. Validate that middleware and programs that connect to the database are efficient in their connection management and do not logon or logoff repeatedly
7. Validate that the SQL statements use cursors efficiently. The database should parse each SQL statement once and then execute it multiple times. The most common reason this does not happen is because bind variables are not used properly and WHERE clause predicates are sent as string literals. If you use precompiles to develop the application, then make sure to reset the parameters MAXOPENCURSORS, HOLD_CURSOR, and RELEASE_CURSOR from the default values before precompiling the application
8. Validate that all schema objects have been correctly migrated from the development environment to the production database. This includes tables, indexes, sequences, triggers, packages, procedures, functions, Java objects, synonyms, grants, and views. Ensure that any modifications made in testing are made to the production system
9. As soon as the system is rolled out, establish a baseline set of statistics from the database and operating system. This first set of statistics validates or corrects any assumptions made in the design and rollout process 

Showcasing Effecta at SAPPHIRE NOW - Prolifics Tool for Test Automation & Data Validation

Prolifics kicks off SAPPHIRE NOW & ASUG Annual Conference this week in Orlando. At the conference, we will be showcasing our SAP testing solutions and share recent success stories with customers like McKesson and Pacific Coast. At booth #2715, we will also showcase a demo of our Test Automation and Data Validation tool - Effecta.

Get a sneak peek of Effecta by viewing the demo below.

Learn more about our SAP testing solutions for our customers here:
McKesson Transforms Business with Script-less Test Automation
Pacific Coast Builds SAP Test Automation Strategy with Effecta

Effecta Demo


To learn more about Prolifics' week at SAPPHIRE NOW, visit: http://www.prolifics.com/sapphirenow-2013.htm

BPM in the Music Industry - IBM Impact Presentation Replay

At IBM Impact, I had the opportunity to co-present with one of Prolifics' BPM clients Broadcast Music, Inc. The exciting thing about this presentation is that it we introduced BPM in the context of the dynamic and rapidly changing music industry. With new digital music outlets such as Pandora, Hulu and others, music is no longer confined to vinyl albums, CDs or traditional venues like live concerts, karaoke bars or radio. Music is truly global and ubiquitous which presents interesting new process challenges for those in the music business.

Take a closer look by viewing my presentation from Impact.

BMI: Innovating the Music Industry with BPM from Prolifics

Want to learn more? Connect with me!
Email - hwebb@prolifics.com
LinkedIn - Howard Webb

For more information about Prolifics, visit: www.prolifics.com

Howard Webb is a Director of Prolifics' BPM Advisory Services. Howard and his team provides consulting and guidance to clients in transitioning to highly efficient Process Managed business models, and equips them for success in their BPM initiatives. For over 25 years he has been a consultant, trainer, facilitator, and speaker on the topics of Business Process Management (BPM), data architecture, and project management. He founded the Midwest BPM Users Group and has published articles on BPM and enterprise architecture. Prior to coming to Prolifics Howard was founder and partner of Bizappia, a consulting and services firm focused on business agility, performance and innovation. Prior to Bizappia, he was a Sr. BPM Technical Specialist with IBM.

API Blog Series Part 2: API Management – The Platform

In my last blog entry, I introduced the concept of API Management and how this area has evolved over the last decade to where it stands today. In this blog entry, I will focus on what are the key components of an API Management platform, what are the different deployment models for the API Platform and who are key players in this space.

What makes up an API Platform?
An API Platform needs to provide the following key components:

• API Builder: Tools for providers to define create and configure an API.
• API Portal: User Interface platform for API providers to socialize APIs with the consumers to enable adoption.
• API Gateway: Manage controlled access to the API layer and protect the services from security threats.
• API Analytics: Provide insight into API usage – operational, technical and business metrics that can help API providers to customize and improves the services they provide.

API Platform – Deployment Models
The following table describes the three common deployment models that are available for an API Management platform.

The Vendor Ecosystem
The recent Forrester report published on Feb 5th 2013, titled ‘API Management, Platforms - Q1 2013’ shows the key vendors who provide the leading platform for API Management today. Another vendor who did not participate in the Forrester survey but that is a strong player in this space is Apigee.

IBM’s API Management Platform [Cast Iron Web API Services] is a strong contender in this space and in my next blog entry, I will focus on how to build an API using Cast Iron.

Rajiv Ramachandran is the Vice President of the SOA & BPM Practice at Prolifics and an IBM Champion for WebSphere. He has 15 years of experience in the IT field — 3 of those years at IBM working in the development teams at its Object Technology Competency Center in Bangalore, India. He was then a Solution Architect implementing IBM WebSphere Solutions at Fireman's Fund Insurance. Currently at Prolifics, he manages a 100+ member worldwide team that focuses on BPM, SOA & Decision Management. An author at the IBM developerWorks community, Rajiv has presented at IBM Impact and IBM WebSphere Services Technical Conference. He holds an MBA from UCLA Anderson School of Management.

Which Cloud Model is the Next “BIG THING?!"

IBM's purchase of Cast Iron resulted in another new integration product in the market by IBM, called IBM Cast Iron. I find this product interesting and started working with the technology. Cast Iron provides an approach to connecting to Public Cloud, Private Cloud and On Premise applications. Recently, a colleague and I presented on this topic at an IBM conference about Cast  and Cloud Computing.

It didn't take me long to understand that the market is buzzing with the term Cloud. It seems everyone wants a piece of it - IBM, Google, Amazon, Salesforce and many other organizations. Naturally, every industry implements its own model and tries to become a market player in this. I started my journey with Cloud recently. Though there are many confusing terms, let’s talk about some business model that Cloud brings us:
a. Software as a Service – SaaS
b. Infrastructure as a Service – IaaS
c. Platform as a Service – PaaS
d. Business Process as a Service – BpaaS

I thought it would be interesting to see which Cloud model is presently more successful, attracts more market and investors and will maintain the trend in future and thereby become the next big thing in market in next decade.

According to market predictions, I found that cloud computing is expected to cross $121 billion by 2015. SaaS holds currently 73% of markets revenues; this is the largest segment of cloud computing services market. IBM is one of the global leaders in SaaS. I have gone through numerous surveys and market research and it is easy to deduce that SaaS is by far the most successful and will remain so for many reasons.

1. Firstly, its price policy is one of the major factors which has made it very popular and unbeatable. This provides better perks for small business and small scale start up companies, allowing them to avoid the high expenses of purchasing and maintaining software. Any extra hardware for setting up the business is dispensable, makes it more cost effective.
2. Secondly, the ability to figure out web traffic in one’s internet based business through different web services such as Google analytics or Google AdWords provided by SaaS makes it very effective to track customer preferences and user behavior and thereby setting the business in the right track.
3. Thirdly, the availability of personalization and customization of application makes it very popular.

Here I should mention that all the above points make SaaS a very cost efficient and practical application for startup companies and small businesses which is one of the most important reasons for the growing popularity of SaaS. To take a deeper look, let’s compare the small business establishment trend and the rising SaaS popularity. An infographic by Intuit explores the costs of starting a new small business in the United States compared to other markets around the world.

http://infographicworld.com/intuit-small-business-in-the-u-s-and-abroad/

The graphic shows that starting a business in the US is relatively easy compared to the largest markets in Asia and a few places in Europe At the same time, user survey analysis conducted by Gartner and others has already discerned that North America is the largest consumer of on demand solutions. This region shows the highest SaaS deployments in expense management, financials, and email and office suites.

Now let’s consider Asia pacific , between 2011 and 2012 we see , SaaS revenue for this region has hiked by approximately $200 million. Asia Pacific includes markets in Australia, New Zealand, Hong Kong, Singapore, South Korea and Taiwan, and emerging markets, including China, India, Malaysia, Thailand, Indonesia, Vietnam and the Philippines. Among them India and China are the leading users of SaaS financial applications. Now if we go back to the infographic by Intuit we can clearly see that the next best countries for starting small business are India and China. This shows a direct correlation between the SaaS usage and their market in regions with booming small business.

It seems the popularity of SaaS will continue in North America especially when the President’s 2013 Budget Bill has given immense importance on supporting small business. The Budget will provide $16 billion for Small Business Administration and thereby expanding small business and in turn generate jobs. Thus SaaS seems to be the next big thing which is here to stay in USA considering its popularity in the small business sector.

Looking at the direct correlation that we observed between the booming small scale and start up businesses in the world market and the growing popularity of SaaS among them, it is easy to conclude that the SaaS Cloud application is definitely the next Big Thing.

Next month, I will be attending IBM Impact in Las Vegas. To learn more about Prolifics' solutions and what we have planned for Impact, visit our conference page.

Note: Market data was referred from Gartner, Intuit and various sources.

Sources:
http://www.ibm.com/cloud-computing/us/en/
http://www.gartner.com/technology/research/applications.jsp
http://www.gartner.com/technology/research/it-spending-forecast/

Arup Datta is a Solution Architect and Integration Specialist at Prolifics and an IBM Champion for WebSphere. Arup has expertise in providing end-to-end solutions leveraging IBM technology across several industry verticals, including Finance, Banking, Retail and Insurance.

Europe's Consumers Embracing Online Retail

British Computer Society (BCS - The Chartered Institute for IT) has highlighted a new report from Forrester Research predicting Europe’s consumers will shun the high street in favour of online over the next few years.

The research firm also predicts security challenges to e-commerce providers, given the annual growth rates and marks UK to be one of the countries leading the way.

Read the BCS News Flash here: http://www.bcs.org/content/conWebDoc/50111

In a recent blog entry, I outlined how Prolifics was able to help a High Street Retail Giant refresh their e-Commerce website using IBM technology. If you missed it, you can read the story here: Prolifics UK Helps High Street Retail Giant Refresh their e-Commerce Website.

Craig Murphy is a Senior Consultant with 13 years experience in the IT industry working with top-tier consulting companies. Throughout his career, he has performed multiple key roles in development & solution architecture, project delivery management and technical sales. His current focus is on Solution Architecture and Application Infrastructure Development for IBM's large Retail Customers. Craig holds a Degree in Computer Science & Information Systems from Rhodes University; is a Certified IBM Professional holding 13 IBM certifications and he is a Professional Member of BCS - The Chartered Institute for IT, making him a world-class resource to his customers, colleagues, and company.