Model deployment
WebSphere Business Monitor Model deployment
This presentation should show you options for development and production deployments of monitor models for use with WebSphere® Business Monitor.
Goals
Goals Show the deployment options for installing monitor models
This presentation will show you how to use the monitor toolkit and administrative console for managing deployments of your monitor models.
Agenda
Agenda Deployment using the toolkit Integrated test client Event recording and playback Test iterations Production deployment using the administrative console Production server un-deployment
This is the agenda for this presentation. You will see how to use the monitor toolkit to deploy monitor models. In addition the presentation will cover tools for testing, such as the integrated test client and event recording and playback. You will review the procedure for deploying monitor models in the administrative console, and you will see some of the unique monitor model pages in the deployment wizard. Finally you will take a look at the procedure for removing a monitor model from a production server.
Deployment using the toolkit
Deployment using the toolkit Install using “Add and Remove Projects…” dialog Single version per model Procedure Generate projects Add projects to the server Emit test events Integrated test client BPC explorer Application emitters Verify results in business space
When you are deploying a monitor model using the toolkit, you can install using ‘Add and Remove Projects’ in the server view menu. In this case, the schema is created automatically along with the Alphablox® cubes. Note that you can only have one version per model in the development environment. First you will need to generate the Java™ Enterprise Edition (JEE) projects using the menu option ‘Generate Monitor JEE Projects’. This creates the Java application which is installed on the server. Next you will add the project to the server using the menu option ‘Add and Remove Projects…’. For testing your monitor model, you have several options. You can use the integrated test client to submit events to the models. In the case of a monitor model based on a BPEL process, you can use the BPC explorer to submit process instances which will emit the events. If you have emitters for your specific application then you can use them to submit the events to CEI. To verify your model logic you can launch business space and view the monitored data in the appropriate widgets in the dashboard.
Integrated test client
Integrated test client
The Integrated Test Client is used to emit sample events for the Monitor test environment server and to quickly and conveniently test a monitor model. The Integrated Test Client panel has two sections, the Add Values to Events section and the Create Test Script section. In the Add Values to Events section, you can select, modify, and add events from the monitor model to the test script. In the Create Test Script section, you can add and edit commands, rearrange events and commands, and import events into the test script.
Event recording and playback
Event recording and playback Use toolkit server menu to manage recording during development cycle Use integrated test client to import the recorded events
The event recording feature allows you to record an event sequence for subsequent playback. This is very useful if you want to iteratively test a monitor model as you continually change and develop the model. For a BPEL application or any other application, you can enable event recording, then manually step through the process or the application which will then generate the event sequence. The event sequence is saved to a database, so then you can replay the event sequence later to re-run the test. You can use scripts or the administrative console to manage these functions. Also, you can activate the event recording in the monitor toolkit. And you can import these events into an integrated test console script. To enable event recording, you can use the administrative pages or you can also use the server menu in the monitor toolkit.
Test environment iteration
Test environment iteration Make changes to a monitor model Update model in the toolkit Generate projects Publish on server menu Auto publish can be selected on the monitor preferences, and this overrides the server settings for auto publish Delete a monitor model Uninstall using “Add and Remove Projects…” dialog
In the toolkit it is easy to iterate in the test environment. For the initial deployment, you can quickly deploy to the server, then use the test client, common base event browser and dashboard to help test the application. When you are ready to make changes, then you can open the monitor model editor in the toolkit to make updates to the monitor model. Then, you re-generate the projects. If the auto publish option is selected in the monitor preferences then the projects are automatically republished to the server. If the republish is not automatic, then you can invoke it yourself in the menu. Then you are ready to test the revised application. In a non-production environment versions are not supported so the republish will replace the existing application and you can test only the latest version. To uninstall a monitor model from the development server, just use the menu option ‘Add and Remove Projects.’
Test server reset
Test server reset The server profile and associated databases are reset to the same state following an initial install of WebSphere Business Monitor. This drops all installed monitor model applications and related runtime database tables. Embedded development server only
To reset the test server profile to the initial state immediately after the monitor install, then you can invoke the manage server profiles option in the toolkit server page. This function removes all monitor model applications and related database tables. If you have added an external server to the servers view, then you will not see the menu option for ‘Manage server profiles’. This feature only works for the embedded server in the monitor toolkit.
Production server deployment
Production server deployment Install EAR using administrative console “New Enterprise Application” link Specify detailed rather than fast path, to see all options Panels to select monitor model options, select Alphablox options, select CEI options, configure security Support for versions - previous version CEI distribution mode set to “active (no new MC instances)”
For a production server deployment, you have much more control over how you deploy the monitor model. In the administrative console, you install the application and there are some pages which are specific for monitor model applications. You have the option to run the schema scripts, to setup cubes, to setup CEI and to configure model security. If this is a new version of an existing model, then you can migrate user-defined KPIs from the previous version. If this is a new version of an existing model then the older versions are set with distribution mode “active (no new MC instances)”. When you are installing a monitor application using the administrative console, you are given the option to show detailed installation options, so you should choose this to gain additional control over the deployment. On the right, you see the four steps in the installation wizard that are specific to monitor models.
Model and Alphablox options
Model and Alphablox options
On the Monitor model options page you can run scripts to create the schema and to enable data movement services. If you enable data movement service when you install the model, data is moved at regular intervals from the operational tables to the reporting tables and terminated instance data is removed, improving reporting performance. If performance is not a concern initially, you might want to perform a simpler installation and choose not to enable data movement service at this time. If you do not choose to run these scripts during installation, they can be run after the monitor model is installed. If the server is in development mode, the database options are disabled, so the model schema is created automatically when the model is installed, and Data Movement Service is disabled. Also, the data movement service option is disabled if the server is configured to use Derby as the database. Select the 6.1 processing strategy to ensure that you are able to use event reordering and the failed event queue. However, only 6.0.2 is available in some cases such models that do not support multithreading or reordering, or if the previous version of the model is in Inactive (event queue recoverable) state. Select event reordering if you have defined an event sequence field in your model and want to ensure that your events are processed in order. This option is not available for 6.0.2 emulation and is optional for 6.1 multi-threaded. If you are installing a new version of an existing model, then you can specify options to copy KPI’s and business situations from the previous version. On the Alphablox options page you can specify the location and security information for the installation of the Alphablox cubes. You will need Alphablox cubes to use the dimensions and reports widgets in the dashboard.
CEI and security
CEI and security
On the CEI options page you can specify the location and security information for the CEI server. Select the event-group profile list name from the list. If this location is remote, ensure that the host name, the RMI port, and security, if required, are entered, and click Refresh to see the event-group list names for that server. You can be given a choice of distribution mode for queue based and queue bypass. If so, consider that queue bypass performs better because processed events are distributed directly into the model's event database tables. For the embedded server in WebSphere Integration Developer, it is only configured for queue-based. For a stand-alone server, it is automatically configured for both queue-based and queue bypass. For a remote CEI server, the person performing the installation and configuration will determine which options are configured. On the security page you can select the resource group for the monitor model. The resource group specifies the users that will have access to the monitor models.
Production server un-deployment
Production server un-deployment Uninstall using administrative console “Uninstall” button on “Enterprise Applications” page For production server, delete scripts are not run automatically so monitored data is preserved For development server, delete scripts are run automatically Version remains in repository and on Monitor models page in administrative console -marked as uninstalled On model version page Run schema delete scripts which deletes monitored data Purge model version on version page Must uninstall EAR and delete schema first; also deletes Alphablox cubes Purge model on model page Run after all versions of a model are uninstalled and version schemas deleted
To uninstall a monitor model from a production server, you can use the uninstall option in the administrative console on the enterprise applications page. Note that the delete scripts are not automatically run on a production server so your monitored data can be preserved for use in dashboards or other reporting. For a development server, the delete scripts are run automatically. Also, the model version remains in the repository so you will see it on the monitor models page of the console, but it is marked as uninstalled. After uninstalling the application for a model version you will run the schema delete scripts which are accessed from the model version page using the option ‘Manage schema’. Then you will purge the model version using the option ‘Purge model version’ on the model version page. Note that you must uninstall the application and delete the schema before it will let you purge. To purge a model and all its versions, you must uninstall all versions of a model and delete all their schemas before you can use the option to purge the model and its versions.
Summary
Summary Covered the development deployment and testing, along with production deployments and un-deployments
In summary, this presentation covered the usage of the monitor toolkit to deploy models and iteratively test them. You also saw how to deploy and un-deploy monitor models in a production environment.
Feedback
Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WBPM_Monitor_Model_Deployment.ppt This module is also available in PDF format at: ../WBPM_Monitor_Model_Deployment.pdf
You can help improve the quality of IBM Education Assistant content by providing feedback.
Trademarks