Welcome
Developing
Source code analysis with code review
With code review, you can create configurations of coding rules for EGL source code. You can then run the configurations to check the source code for consistency with the rules.
Creating user-written rules
User-written rules are implemented by Java™ classes that call EGL code analysis APIs.
Installing a plug-in
After you create a plug-in, install it into the development workbench environment.
Adding a feature to an update site
After you add a plug-in to a feature, you must add the feature to an update site.
Updating a feature in an update site

Overview
Getting started
Installing
Upgrading and migrating
Developing
- Model driven development of EGL code
- Generating source code from UML models
  You can use transformations to create source code from a UML model. First you must create a transformation parameters file and then apply those parameters to a model.
- Generating the EGL Dependency Graph from EGL projects
- Generating Source Code from OpenAPI Documents
- Developing EGL applications
  Enterprise Generation Language (EGL) is a programming language that you can use to focus on business problems instead of software technologies. Within the Rational® development environment, you can use EGL wizards and other tools to write complex applications with minimal effort.
- Source code analysis with code review
  With code review, you can create configurations of coding rules for EGL source code. You can then run the configurations to check the source code for consistency with the rules.
  - Overview of software analysis
    In a software analysis, a configurable set of coding rules is applied to a specified group of source code files. Results are generated that identify lines of source code that violate a rule.
  - Supported features
    The code review component includes features for creating and enforcing coding rules for EGL in the Linux™ and Windows™ environments.
  - Installing the code review component
    Install the code review component with the IBM® Installation Manager.
  - Doing basic tasks with the software analysis configuration window
    You can open the software analysis configuration window and switch modes.
  - Creating a software analysis configuration
    Create a software analysis configuration to define coding rules and to specify source code files to be checked.
  - Running a code review
    A code review can be started from the workbench toolbar, the software analysis configuration window, the project explorer view, or the navigator view. The method of starting the code review can override the scope that is defined in the software analysis configuration.
  - Viewing results
    After you run a code review, you can view the results that are generated.
  - Fixing a problem reported in a result
    You can modify a source code file to fix a problem that is detected by code review.
  - Custom categories and rules
    A custom rule is a built-in rule for which you specify one or more parameters that affect the behavior of the rule. A custom category is a folder for storing custom rules.
  - Creating user-written rules
    User-written rules are implemented by Java™ classes that call EGL code analysis APIs.
    - Generating a plug-in project for a user-written rule
      To generate a plug-in project for a user-written rule, run the New Plug-in Project wizard and select the Custom EGL Code Review Rule template.
    - Generated files: Rule and category extensions
      The New Plug-in Project wizard generates a plugin.xml file that includes a rule extension for each new user-written code rule. The wizard also creates a category extension if the category to which the rule belongs does not exist.
    - Generated files: Implementation code
      The New Plug-in Project wizard generates a Java™ package and class for implementing EGL user-written rules.
    - Coding analysis methods with the EGL APIs
      Use the EGL APIs to analyze the EGL language elements that you select for your user-written rules.
    - Installing a plug-in
      After you create a plug-in, install it into the development workbench environment.
      - Adding a plug-in to a feature
        Before a plug-in can be installed, it must be added to a feature. The feature contains additional information about the plug-in that is required by the update application. A single feature can contain multiple plug-ins, fragments, and other files.
      - Adding a feature to an update site
        After you add a plug-in to a feature, you must add the feature to an update site.
        Publishing a feature on a site
        You can publish a feature on a site.
        Updating a feature in an update site
      - Installing, uninstalling, or updating a feature
        After you add a feature to an update site, you can install the feature into the product environment, update the feature, or uninstall it.
      - Sharing an update site
        You can make an update site available to others so that they can install your feature.
      - Finding feature updates
        A user who installed one of your features might want to know when a new version of the feature is available. You can configure the product to automatically notify you when an update to a feature is available, or you can check for an update manually.
    - Adding a rule to an existing rule plug-in project
      You can add a user-written rule to an existing custom-rule project.
    - Working with the EGL APIs for code review
      The Custom Rules API for EGL code review and the EGL Application Model API are complementary. Some knowledge of both is required to implement a user-written rule.
- Responsive Design Support in RBD
  What is Responsive Design? Responsive design is an approach for creation of web pages that automatically scales its content and elements to match the screen size on which it is viewed. So, instead of designing multiple websites for different devices with variable screen sizes, we can design just one website that scales up or down automatically, to match the device it’s being viewed on.
Samples
Troubleshooting and support
EGL runtime error messages
Reference
Glossary
Using the help
Notices for IBM Rational Business Developer documentation

Updating a feature in an update site

About this task

When you update a feature and want to publish the updated version, you have two options:

You can add the updated version to the update site. Update sites can contain multiple versions of the same feature, even if the content and the version numbers of the features are identical. This addition is possible because the site manifest editor includes the current date and time in the name of each feature JAR file, making each name unique.
You can delete the old version from the update site and then add the new version.

Procedure

To add an updated version of a feature to an update site:
1. Optional: Before you add the updated version of the feature to the update site, you can modify the version number of the feature.
2. Complete steps 4 through 8 in Publishing a feature on a site.
To delete a feature from an update site:
1. Open the update site in the site manifest editor.
2. In the list of features, right-click the feature that you want to delete and then click Delete.