WebSphere and CICS Support, including the IBM Business Process Management products, have a significant Social Media presence. During the last couple of years, we've grown our presence in the Social Media space to better serve you. You can see us on Twitter, Facebook, and on our two blogs: WebSphere and CICS Support and the IBM Business Process Management Products Support Blogs. For more information on our Social Media presence, see our WebSphere and CICS Support Blog: http://www.ibm.com/developerworks/mydeveloperworks/blogs/aimsupport/entry/how_social_are_we
IBM Business Process Management Products Support Blog
Bill Wentworth 120000G5ES Tags:  blog facebook twitter social_media cics websphere 9,818 Views
Scarlet O'Hara once said "I'm going to live through this and when it's all over, I'll never be hungry again." That was a story and era before computers. These days our computers can become starved, at least the Java (tm) virtual machine (JVM) can. Performance is a key concern for everyone. When users have to wait, they are discouraged and either become distracted or they go somewhere else. Keeping a system running smoothly is key. Every now and then systems will have a slow spot. However, when it continuously impacts users, this issue must be investigated. For this article, I am focusing on the following example outputs seen in an JVM SystemOut.log. These examples came from an IBM Business Process Manager SystemOut.log file.
HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 23 seconds.
DCSV0004W: DCS Stack DefaultCoreGroup at Member PCCell01\PCNode01\BPM751PDEV.AppTarget.PCMNode01.0: Did not receive adequate CPU time slice. Last known CPU usage time at 12:23:55:452 CST. Inactivity duration was 31 seconds.
What does CPU Starvation mean?
Where is all the CPU time going?
If the operating system does not have any extra processes and you see CPU starvation, most likely the server is a guest operating system on a virtual environment. What this means is the larger virtual infrastructure does not have enough CPU time to give all of the virtual machines it controls. Contact your virtual machine provider or internal sysops team to start investigating the overall health of the virtual system. Other virtual machines in the environment might be using the system heavily and need to move to a different server. Another option would be to dedicate CPU usage rather than sharing, which is default. We have a document that offers links to other documents to consider when you are running J2EE applications and databases in a virtual environment.
Have a good day and don't starve!
MarkFilley 27000392R8 Tags:  policy practices profile backup file procedure best database system dba bpm 1 Comment 16,221 Views
Always! No, really. Proper backups are like brushing teeth and flossing. Doing it regularly keeps you healthy! The IBM Business Process Manager system has three components that you should backup regularly: profile (file system), database, and applications. Backing up each of these components is critical for the emergency we hope to never face. Application roll outs, interim fix installs and version upgrades should all work the first time and deliver the desired results. As we all know, there are times when the install fails and we need to roll back. Thankfully rolling back is easy when you take proper backups.
Some fixes and fix packs for IBM Business Process Manager require profile and database upgrades. In the interim fix installation, it is stated to backup your profile and backup your database. The profile is located in the installation directory at [install_dir]\profiles using the backupConfig command or just a simple .zip file of the profile is a good backup. Contact your database administrator about backups before installing interim fixes that require upgrade_7x. This step is critical because if any part of the install process fails, the system can be restored to a known state. This best practice has saved many customers from disaster.
What about after the fix is successful? The fix installs without errors, the server starts up without errors, and you test the basic functionality and run through a user acceptance test or load test of your application. The results are all clear and any issues you have are resolved or the new desired functionality works. Should you take a backup now? YES! Why? One basic reason is this is now a good known working condition. Consider the following scenario. You encounter a known problem and apply the interim fix to resolve the problem. The system now works as expected and development continues. Some time passes and the system starts to exhibit problems. Having a backup after the interim fix install enables you to roll back the system and avoid having to re-install the interim fixes.
Databases are often on a daily or weekly backup cycle depending on the nature of the system (Test vs. Production) and company policies. The database is the heart of the IBM Business Process Manager system; it contains all of the data for tasks and instances and the application solutions. As the administrator of the IBM Business Process Manager system, be sure you know when the database is backed up and how to reach the database administrators to restore databases in case of an emergency.
For the process applications, export your application at major milestones to a safe location outside of the Business Process Manager system. The production environment has all of your business data, but the applications are the key source code to those applications. The Process Center is the repository. If for some reason the Process Center becomes corrupted in some way, you have an external backup of your application code and could easily make a new Process Center with the applications that are in production. Treat the process application exports like source code and keep them stored in another location in case they are needed.
If you have any feedback on this blog, leave us a comment and we will respond as quickly as possible!