IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Manage builds

Build Activities view

In IBM Integration Designer, the Build Activities view is the designated tool for managing builds. It features a simple user interface that enables you to easily select build activities for both automatic and manual builds and invoke immediate manual builds that are independent of your build activity selections. The Build Activities view also enables you to view the build and server status of business integration projects as well as the operational state of supported servers.

In the Business Integration perspective, you can open the Build Activities view by clicking the Build Activities tab. (If the Build Activities tab is not visible, you can open it by first opening either the Business Integration view or the Physical Resources view and then clicking the Show Build Activities View icon

.) The Build Activities view is shown in the following figure:

As shown in the figure, the Build Activities view has three sections:

These three sections are described in the following sections.


The "Select workspace activities to run during a build" section

In this section of the Build Activities view, you can specify the build activities that you want to have invoked whenever an automatic build or a manual build occurs as a result of selecting one of the following menu items from the Project menu:

The Select workspace activities to run during a build section contains three radio buttons:

If the Validate button is selected, all workspace resources are validated whenever a build occurs.

If the Validate and update deploy code button is selected, all workspace resources are validated and deploy code is generated whenever a build occurs. (This is the default selection.)

If deploy code has not yet been generated for one or more of your integration modules or component test projects, selecting this button will invoke an immediate build and the generation of deploy code.

If the Validate, update deploy code, and update running servers button is selected, all workspace resources are validated and deploy code is generated whenever a build occurs, plus any integration modules or component test projects that currently reside on running servers will be automatically updated on completion of the build. If deploy code has not yet been generated for one or more of your integration modules or component test projects, selecting this button will invoke an immediate build and the generation of deploy code, plus any integration modules or component test projects that currently reside on running servers will be automatically updated when the build completes.

Whenever a build occurs, all of the buttons are disabled until the build has completed.

If you close the Business Activities view after selecting one of the buttons, your selection will be retained even though the view has been closed.


The "Manual triggering of workspace build activities" section

In this section of the Build Activities view, you can invoke immediate manual builds that will temporarily override your build activity selections. The Manual triggering of workspace build activities section contains two buttons:

If you click the Update Deploy Code button and your deploy code is not currently up-to-date, an immediate manual build is invoked that validates your resources and generates deploy code. If your deploy code is already up-to-date, a build will not occur and a message will explain the reason. If that the Update Deploy Code button has a corresponding menu item (Projects > Business Integration Projects > Update Deploy Code) that has the same behavior as the button.

If you click the Update Running Servers button and your deploy code is not currently up-to-date, an immediate manual build is invoked that validates your resources, generates deploy code, and updates any integration modules or component test projects that currently reside on running servers.

If your deploy code is already up-to-date and the integration module is already synchronized with the server, a build will not occur and no attempt will be made to republish the integration module on the server. A message will be displayed to explain the reason. If that the Update Running Servers button has a corresponding menu item (Projects > Business Integration Projects > Update Running Servers) that has the same behavior as the button.

Whenever a build is invoked, both of the buttons (and their corresponding menu items) are disabled until the build has completed.

In some instances, you may find that simply generating deploy code and updating your existing projects on the servers is not sufficient to keep the projects in your workspace synchronized with the projects on the servers. For these situations, a Project > Business Integration Projects > Regenerate Deploy Code and Reinstall Server menu item is provided to help you accomplish one or more of the following tasks:


The "Project status" section

In this section of the Build Activities view, you can view the build status and server status of business integration projects as well as the operational state of supported servers. The section is automatically updated at the completion of each build or server event. The Project status section consists of a table with the following columns:

The Name column displays the name of each business integration project in the workspace and it also displays a symbol that identifies the specific project type, such as integration module, library, or component test project.

The Validated column indicates whether a business integration project has been validated.

If errors are detected in a project during a build, the column will also display an error symbol and the number of errors detected.

The Deploy code updated column indicates whether deploy code was generated for an integration module or a component test project. If errors are detected in the associated Java 2 Platform Enterprise Edition projects, the column will also display an error symbol and the number of errors detected. (If that Not applicable is displayed for all libraries because deploy code is never generated for libraries.)

The Status on server column shows the status of an integration module or component test project on the server. The column heading takes the form "Status on server_state server server_name", where server_state is the current state of the server (starting, started, stopping, stopped, or publishing) and server_name is the name of the supported server (such as WebSphere Process Server v6.2 or WebSphere Enterprise Service Bus v6.2). There is one Status on server column for each supported server listed in the Servers view.

For example, if there are two supported servers listed in the Servers view, then there are two Status on server columns listed in the status table. However, if there are no supported servers listed in the Servers view, then no Status on server column is displayed in the table.


Project statuses

In the Status on server column of the project status table, a project can have one of several statuses, such as:

The Not applicable status is displayed for all libraries because libraries do not get deployed to servers and therefore do not have any status on servers.

The Ready to run status is displayed for a module when it meets the following conditions:

The Not ready to run status is displayed for a module that exhibits one of many possible conditions.

The Build Activities view ignores changes in the .settings folder of business integration projects (such as modules and libraries), but the Servers view is aware of any changes in the .settings folder and it updates the status of servers accordingly. As a result, the Build Activities view will display a status of Synchronized for a server whenever the .settings folder of a project is changed, but the same server in the Servers view will display a status of Republish. The reason that the Build Activities view ignores changes to the .settings folder is because the resources in the .settings folder are not required by the server to run the application. By comparison, the Servers view marks all changes to the resources in the .settings folder regardless of whether the resources are actually needed by the server. Generally, if the Build Activities view shows a server status of Synchronized and the Servers view shows a server status of Republish, the Build Activities view is correct and you do not need to republish to the server.

Manage builds