Preparing a monitor model for a production environment

After you have finished creating and testing your monitor model, you can deploy the monitor model application in a Business Monitor production environment. First, generate Java™ 6 Platform, Enterprise Edition (Java EE) projects from the model and export the model as an Enterprise Archive (EAR) file.

1. Right-click the monitor model in the Project Explorer view, and click Generate Monitor Java EE Projects. The Generate Monitor Java EE Project window opens. (If you want, you can set a preference that enables you to specify templates for automatically populating the text fields with default project names, as described in the topic Setting preferences for generating Monitor Java EE projects.) You can accept the default names for the projects, but be sure that the names are not too long. In Windows, there is a maximum path length of 256 characters, so any path longer than 128 characters at creation time likely causes problems by the time it is published. If the monitor model name or path name is too long, a monitor model application does not show up as started in the Integration Designer servers view or in the WebSphere® Application Server administrative console.
   Note: When you generate Java EE projects for large monitor models, it is possible that you might experience an out-of-memory condition in the Eclipse workspace of IBM® Integration Designer. Information about resolving these out-of-memory conditions is found in the topic Java EE project generation results in an out-of-memory condition.
2. If any of the Java EE projects exist, select Overwrite existing projects to continue. If Clean build is selected and the projects have already been added to the server, the projects are stopped, removed from the server, deleted, and re-created. If you have generated the projects before and have made only non-structural changes to the monitor model (such as changing descriptions and changing expressions), you can clear Clean build to speed up code generation. The contents of the projects are refreshed in place and the projects are added to the server after the contents have been refreshed.

   This step assumes that Automatically republish project to Server is selected on the Business Monitoring preferences page (Window > Preferences > Business Monitoring). Although you must still add new projects to the test server, the generated Java EE projects automatically replace currently published projects. If this option is not selected and the project has been previously published, you must manually remove the project from the server before generating the Java EE projects. After you generate the Java EE projects, you can add the project to the server again.

3. Optional: If you want to run the code generation in the background and access your workspace at the same time, click Run in Background when code generation begins and the Generate Monitor Java EE Projects window is displayed. The window closes, and a progress bar is displayed in the lower-right corner of your workspace. Click the progress icon at any time to view the progress. From the Progress view, you can also cancel a code generation job that is in progress.
   If you accept the default names, the following two Java EE projects are generated from the monitor model:

   Name	Description
   fileNameModelLogic	An EJB project that contains the event processing logic of the monitor model
   fileNameApplication	An enterprise application (EAR) file project that contains the 2 EJB projects

   Make sure that the code generation task has completed before attempting to export the EAR file.
4. From the main menu bar, select File > Export. Expand Java EE and click EAR file. Click Next.
5. Select the EAR file application corresponding to your monitor model.
6. Click Browse to select the destination directory, and type a name for the EAR file. Click Finish.