Product: WebLogic Communications Platform Archives
Reduce the Risk from Changes to US Daylight Savings Time
Posted by iang on March 2, 2007 at 8:03 AM | Permalink
| Comments (1)
The US Energy Policy Act of 2005 resulted in changes to the timing of Daylight Saving Time (DST) in the United States. These changes could have a serious impact on your systems and are effective as of March 11, 2007.
Customers running BEA Guardian with the March 9th signature release (1.0.3) will have this issue automatically identified. (If you're already running Guardian, just click "Update" to get the latest signatures.) In addition, they will be provided with notification of specific instances where it is a threat and offered recommended solutions.
WebLogic Server relies on the time conversion functions provided by the Java Virtual Machine (JVM) for reporting the local time. If your system relies on the US time zone calendar, the underlying JVM being used by WebLogic Server must be upgraded. These DST time zone changes have been incorporated into the following JVM releases:
- Sun JDK 1.4.2_11
- Sun JDK 1.5.0_06
- BEA JRockit 1.4.2_11 R26.4 and later
- BEA JRockit 1.5.0_06 R26.3 and later
Check out BEA Guardian at http://www.bea.com/support/guardian to learn more about how Guardian can protect you.
Signatures are easy to write... earn $50 for your idea!
Posted by iang on February 16, 2007 at 2:24 PM | Permalink
| Comments (0)
Think about the last support case you had to open for one of your BEA products. If it's been a while, you can always jog your memory by logging into eSupport to look at your case histories.
Now think about what caused the problem you reported. Was some part of your system configuration just a little off? Was there a software bug? Was there some problem in the interaction between your BEA product and another vendor's software or hardware? How would you describe the problem in one sentence?
When the Developer Relations Engineer (DRE) started working on your case, what did you talk about? Odds are good that at the very least, you identified the product versions and some of the configuration settings in play.
Could the same problem occur somewhere else in your environment? What conditions would you need to identify in order to determine that?
Finally, what did you do to resolve the issue? For example, did you modify a configuration setting? Was a patch or maintenance pack identified? Did you make any changes to other 3rd party products to integrate with your BEA products?
OK, you're done!
That's all it takes to submit an entry to the Guardian Signature Sweepstakes. You can submit up to three entries per day for a chance to win a Ducati racing super-bike or US $30,000 in cash. If you're one of the first 500 qualifying submissions, you also get a $50 American Express gift certificate.
How many signature ideas can you come up with now?
What about some of the issues you were able to resolve yourself (perhaps only after some time-consuming research and troubleshooting)? Wouldn't it be nice to have a signatures for these kinds of issues, too?
Download BEA Guardian here to see how we're using signatures today to help you identify problems before they occur.
Preemptive Support
Posted by iang on January 25, 2007 at 11:54 AM | Permalink
| Comments (4)
What It Isn't
Traditional customer support in the software industry has always been reactive: you encounter some problem, you do a bunch of time-consuming research and troubleshooting, you report it to your vendor's support organization. You wait for a resolution.
What It Is
Pre-emptive support turns that model on its head by using software to check for potential problems before they become actual problems. BEA Guardian is that software.
How Does It Work?
Let's start with the facts: software vendors' support organizations know a lot about the kinds of issues you encounter when you run their products, and the experts in the support organization know how to resolve those issues. The problem has always been about how to share or distribute that vast collection of specialized knowledge and expertise to the right customers. BEA Guardian solves that problem: each potential problem is encapsulated and described in a signature. Guardian evaluates signatures against your target systems and makes specific recommendations for how to avoid the problems you may encounter.
What is a Signature?
A signature is an XML document which describes a potential problem. It includes instructions for Guardian to determine whether this signature is "detected" in your target system, and each signature provides user-friendly recommendations for how to resolve any issues that are detected.
BEA Support has already written lots of useful signatures which are helping our customers prevent potential problems from becoming actual problems. Do you want to help us? Check out the Guardian Signature Sweepstakes.
|
