Forum Guidelines
Please be aware of the following guidelines when participating in the Jazz Forum. General

The forums are a user-supported platform; some of the users are also developers of the ELM products. Be considerate of your fellow users. If you need formal product support, contact IBM support.

  • Language: English
  • Netiquette: Be nice!
  • Content:
    • Non-English language content will likely be banned.
    • Content with ads or links to ads will be banned, along with the user account.
    • Pointless responses, especially to old, often seen answers, that produce links to training sites, will be banned after a day or two.
    • Please note that the forum is not a JavaScript, Java, Eclipse, development help tool. If you have questions regarding general language features, please ask on other sites like StackOverflow.
  • Profile: If you have issues with your profile or need it deleted, send an email to
Asking Questions
  • The forum supports these features in questions. Please use these features to your advantage.
    • Subject - a short summary of your question.
    • Question - a longer description of your question.
    • Comments - one or more comments, clarifying questions, or remarks on a question or an answer.
    • Answers - One or more answer to the question. If your question gets answered, please accept the answer.
    • Tags - to mark the question with a product name and more context.
  • Please make sure that your questions are in the context of the products that are available for download from, including Engineering Lifecycle Management, Engineering Workflow Management, Engineering Requirements Management DOORS Next, Engineering Test Management, Rhapsody Model Manager, Jazz Foundation, Engineering Method Composer, Engineering Insights, Publishing, Jazz Reporting Service, Global Configuration Management, and Engineering Integration Hub.
  • It is always a best practice to search the internet for similar questions and answers before asking. If you are using a search engine, you can usually append to limit the search scope to this site. If you find related questions and answers, see if they address your question. If not, or the information is not sufficient, please ask your own question here. You may want to include a reference to the prior answer that did not meet your needs.
  • Please do not ask additional unrelated questions as part of an existing question. Create your own new question. You could use a comment for clarification in an old question, but usually you should consider creating a new question. This is especially true if the question is several months old.
  • Use the question, comment, and answer features of the forum to make it as useful as possible.
  • Try to create a good subject that touches on the problem and really is a question. Do not simply paste your question into the subject.
  • Tag the question with the product name you are using. Choose one or two additional reasonable tags. If a tag is unfamiliar to you, don't choose it. For example, [jazz-foundation] is a very popular tag that is used often but probably fits 2% of the cases where it is used. If there is no matching product name of the form for your problem, consider finding another forum that deals with the product and question you have. If you have questions about the API use [extending] (for Java API) or [OSLC] or [REST] for web-based API as tag. If you ask about EWM JavaScript or how to modify work items use [attribute-customization] as tag. If you have questions around agile methodologies use [agile] as tag. Don't use it just because you have the agile template deployed or because it is popular today.
  • In the question body,
    • Clearly describe what you do or want to do and provide sufficient detail about the problem/question.
    • Explain why you want to do this and what you want to achieve with it. Often problems are not problems in the tool but knowing how to achieve certain goals; knowing what the intent is often directs to completely different answers. Do not ask “we require the tool to work this way”.
    • Provide the tool name and the version of the tool you use.
    • If there are errors, provide the error message. Before you ask the question, carefully read the error message, think about it and what it means and ideally check the application log files.
    • If this is around setup, upgrade, and similar, provide the information about the topology you use, the operating systems, their versions, the databases, their versions, the application servers, and their versions; that is, anything that might be special in your environment could be of interest.
    • If you use a UI, provide the information about which UI you use, browser, other client, etc.
    • Use screen shots where possible. Please note that you need a reputation of 50 or higher on the forum to post image. If you don't yet have that reputation, you can upload the screen shots to some other site and put the link into the question.
API Code
  • Don't just paste your code in a question and hope someone will remote debug your code. All the users here are professionals and have a day job that does not leave them the freedom to do this.
  • If you want to discuss code and have an error that shows with the code, carefully consider the error. Provide the error message and the line it occurs in addition to the code in the question. Looking into the log files before doing this, applies again. Make sure to point at the line that throws an error in your code, as only you can do that.
  • If you want to discuss code, you should be able to debug it. If you are not, get your debug environment up and running for the server and the client API. Run the snippets that come with the Plain Java Client Libraries and understand the basic structure for EWM automation using the Java API. Consider following this post about getting started using the API.
  • If you want to extend the EWM server, run the whole Engineering Workflow Management Extensions Workshop before you try anything yourself.

  • Before you ask JavaScript related questions, read the provided Wiki information, especially the API for JavaScript section and carefully read the Process Enactment workshop lab 5. Ideally run the workshop.
  • Make yourself aware that the JavaScript API is limited, and you cannot get to all the information you might like. Learn how to debug JavaScript where you can debug it.

Note on Extending

Please be aware that extending the tools should not be taken lightly. It is expensive, takes skills, needs to be maintained, can have impact on performance and, in general, requires user experience. Never do it because it can be done. There must be a real business case to consider extending the tools. The fewer you extend, the better.