OptimalJ Problem Resolution ProcessProduct Usability
For assistance with product usability issues (e.g. how-to questions), please follow these steps:
- Review the information in the OptimalJ Documentation and FAQs on FrontLine (registration required).
- Also, on JavaCentral (login required), review the white papers for articles on using OptimalJ.
- Search the OptimalJ Forums (login required) for information that may be contained in a posting of a related topic.
- If these resources do not answer your question, submit a question to the OptimalJ Forums.
Please note that you will need to register at the JavaCentral website to access the OptimalJ Forums and the white papers.
Product Problems Supported Release Policy
Please read the Supported Release Policy for details about the support policy for development and deployment issues. Call Logging Process
If you are a licensed OptimalJ customer, you have access to qualified engineers who can help determine the nature of the problem and provide solutions to your issues. To expedite the process, please follow these steps:
- Check whether the issue you are experiencing is known via the Known Software Problem List and FAQs
- Log a call to Customer Support . For a high-priority issue, please contact your support center by phone.
- When logging an issue, please provide the following information:
- Company name
- Company client number (issued to you by Compuware)
- Contact person’s name
- Phone number
- Fax number
- E-mail address
- Product name, edition, version number, and service pack level
- Operating system (include name and version)
- JDK version
- Application/EJB/Web server (include name and version)
- Database (include name and version)
- EJB Version
- Description of the problem, including error messages
- Steps to reproduce the problem
- Problem priority level (see below for description)
Call Resolution Process
After reporting the issue, you will receive a unique eight-digit call tracking number. This tracking number will be used to track all conversations and activities surrounding your call. Your call will be dispatched to the appropriate expert in one of the following areas:
- OptimalJ technical issues
- License administration and contracts
Your assigned expert will work with you to recreate and solve the problem. If the issue cannot be satisfactorily resolved at the first level of contact, each product expert has their own escalation process to keep open calls moving towards completion.
Description of Priority Levels
When logging a call, you will be asked to assign a priority number to your issue. The following table provides a guideline to help you assign a priority to your issue.
| Priority |
Response Time |
Description |
1 (Critical Problem)
|
1 business hour
|
- No known workaround or solution to the problem at the time the call is logged
- Causes the software or operating system to fail completely
- Requires constant restarting of the software or operating system
- Results in corruption or loss of data
- Prevents the installation of the software
|
2 (Major Problem)
|
4 business hours |
- No known workaround or solution to the problem at the time the call is logged
- Prevents the use of an explicitly documented major function of the software
- Causes a software or OS crash
- Use of the software is seriously impacted (mission critical usability problems)
- Installation issues
|
3 (Normal Problem)
|
8 business hours
|
- It does not meet the criteria of a priority 1 or priority 2
- Product does not work as explicitly documented
- Non-mission critical usability issues
|
4 (Minor Problem)
|
2 business days |
- It does not meet the criteria of previous priorities
- Low priority requests for information (e.g. what is the most current release?)
- Documentation errors
|
|
 |