Generate executable artifacts for the monitor model and deploy to the server

Now you will use WebSphere^® Integration Developer to deploy the monitor model to the WebSphere Business Monitor server.

1. Generate the model.
   1. In the project tree, expand clips > Monitor models > clipsbpm.mm. Right-click clipsbpm.mm and select Generate Monitor J2EE Projects. When generation is complete, select Finish. A progress dialog box shows the status of the operation and it closes when the operation is complete. This will take a few minutes.
   2. Check for errors in the Problems view. There might be warnings, but there should not be any errors. If you see errors, rebuild by selecting Project > Clean. Select Clean all projects, and then click OK.
2. Next regenerate the forms user interface for the Order Handling process.
   1. Click the Business Integration tab in the left pane.
   2. Right click on ClipsAndTacksF1 from the left pane and select Generate User Interfaces.
   3. Select IBM Lotus Forms client as the Generator type, and click Next.
      

   4. Name the dynamic Web project ClipsAndTacksUI. For the style, select IBM Style and click Finish.
      

   5. When you see the Client generation completed message, click OK.
      

3. Deploy the generated projects.
   1. Click the Servers tab and then right-click WebSphere Business Monitor v6.1 on WebSphere Process Server and select the Start option to start the server. Starting the server might take a few minutes.
      

   2. After the server has started, right-click WebSphere Business Monitor v6.1 on WebSphere Process Server again and select Add and Remove Projects.
   3. Move ClipsAndTacksF1App, ClipsAndTacksUIEAR, and clipsbpmApplication from the list of available projects to the list of configured projects (you can use Add All if there are no other projects in your workspace) and then click Finish. A progress message displays in the lower right-hand corner of the window. Deploying and starting the applications might take a few minutes.
   4. Check the messages in the Console view for errors. Note that because the application was just installed, there are no values for the KPIs and other metrics yet. The Console view will show warning and error messages to this effect. The messages will be from the kpi package and indicate a divide by zero exception. This is expected until Orders are processed. The messages will repeat every minute until an Order is processed. This is because earlier in the model it was specified to check the KPI based on a “recurring wait timer” set at 1 minute.
   5. In the Servers view, right-click and select Run administrative console. The administrative console will open in a new tab.
   6. The administrative console will prompt you for a user ID and password. For the user ID, enter admin. For the password, enter admin Click Log in.
   7. Select Applications > Monitor Models.
      

      If the application starts, it will show a green status. If the status of clipsbpm is red, then it is stopped. Wait a moment and then refresh the process by clicking the icon to the right of Status in the last column of the table. You should see green to indicate that the model has started. If the model does not reflect green, wait a few more minutes and refresh the display again.

   8. In the Console view, check the server log to ensure that there are no problems other than the KPI divide by zero exception mentioned earlier that is due to no orders having been processed yet.
   9. By using the integrated WebSphere Business Monitor server in WebSphere Integration Developer, you do not need to set up WebSphere Business Monitor data security because the administrator is automatically authorized to access all models. When using an external server in future projects, open the administrative console, navigate to Security > Monitor Data Security, and then add the model, role, and user information to a resource group.