Modified on by Bill Wentworth
This blog entry is an addendum to the detailed migration procedure from WebSphere Process Server V7.0.0 to IBM Business Process Manager Advanced V8.0, which was described by Sharath Srinivas here. The document was co-authored by Werner Tod and Matthias Benda, who are IBM consultants for the IBM Business Process Management family of products.
This blog describes the necessary extra steps for the migration of a WebSphere Process Server V7 environment with WebSphere Business Monitor V7 that is implemented in the same WebSphere cell.
To ensure the proper sequence of migration steps, we reference the migration step numbers from Sharath’s migration procedure. In case we need to add activities to a migration step, we add an “A” to the original step number. For example, “1A”.
For details regarding the individual migration steps, see the corresponding information in the IBM Business Process Manager and IBM Business Monitor V 8.0.1 product documentation.
2A. In addition to IBM Business Process Manager V8.0.1 Fix Pack 2, also install IBM Business Monitor 8.0.1 Fix Pack 2 on the target systems.
2A.1 Select to automatically deploy Cognos BI service, which used by IBM Business Monitor instead of the previously used AlphaBlox, during the profile migration process or manually by running the configuration wizard from the administrative console. To deploy Cognos BI automatically during the profile migration process, you must set some parameters for deploying the Cognos BI service. Even if your source version is 7.5.x, you must set the parameters because the Cognos BI service configuration cannot be migrated to the target environment without setting the parameters.
Complete the following steps:
(a) From the install_dir/scripts.wmb/migration/ directory, run the CognosConfig script.
(b) From the command line, set the following parameters to appropriate values: Cognos database, Cognos database username, Cognos database password, Admin user name, Admin password, Cluster/Server/Node.
(c) Manually publish the cube after completing the product migration:
1. Open the Admin Console at Applications > Monitor Models.
2. Select the version of a monitor model under Version properties.
3. Click Manage Cognos cubes.
4. Select the monitor model version and click Publish
Before creating the snapshot of the source profile, you have to migrate the WebSphere adapter configuration (if you use additional adapters) and copy the third-party libraries (if you use any in your environment). The adapter migration is described in detail in the IBM Business Process Manager and IBM Business Monitor product documentation. Make sure that your third-party libraries are compatible with the target version of IBM Business Process Manager and that they are copied to the same location as in the source environment.
In some cases, the old host names still show within URLs in the target profile. You have to replace those occurrences in the target environment before you can continue!
Steps 21A and 22A:
The database schema upgrade also has to be applied to the Monitor database. Create and run the appropriate scripts in addition to those for the Common database and the BPC database.
After upgrading the schema of the Monitor database, you also have to migrate the existing Monitor data:
Run the DataMigration script to migrate the database: 801monitor_root/scripts.wbm/migration/DataMigration/DataMigration.sh
Run the DataMigration script using the following parameters:
DataMigration.sh -dbType database_type -dbName database_name -dbSchema database_schema_name -host database_host_name -port database_port -dbUser database_user_name -dbPassword database_password -dbDriverType jdbc_driver_type
database_type is the type of database. The value must be one of the following values:
database_name is the name of the IBM Business Monitor database (by default, MONITOR)
database_schema_name is the schema name of the IBM Business Monitor database (by default, MONITOR)
database_host_name is the fully qualified host name or IP address of the node where the IBM Business Monitor database is installed
database_port is the database port
database_user_name is a user with access to the IBM Business Monitor database
database_password is the password for the user
jdbc_driver_type is the JDBC driver type that is used to connect to the IBM Business Monitor database. This parameter is required only when the database type is DB2ZOS. The value must be 2 if the database is local and 4 otherwise.
If you chose to deploy the IBM Cognos BI service automatically during profile migration, you must create the database that IBM Cognos BI uses for the content store. If the database that the IBM Cognos BI service uses for the content store is a remote database, ensure that a local database client is installed on the Cognos server and that the MONITOR database is cataloged. The cataloged database name must match the database name that is configured in the WebSphere data source for the MONITOR database.
To create the database that IBM Cognos BI uses for the content store, complete the following steps:
From the IBM Business Monitor V8.0.1 monitor_root/dbscripts/Cognos/DB2/ directory, open the createDatabase.sql script in a text editor and change the database name.
Replace the values for the following variables with the values for your environment:
@COG_DB_NAME@ - Required for SQL Server and DB2 on z/OS
@COG_DB_PASSWORD@ - Required for SQL Server and Oracle
@COG_DB_USER@ - Required for SQL Server and DB2
@STORGRP@ - Required only for DB2 on z/OS
@TSDIR@ - Required only for Oracle
@SCHEMA@ - Required only for Oracle
Save your changes and close the file. Important: If you are using a remote database and prefer not to run the scripts on the installation program of the database server, you must copy the scripts to the database server before continuing.
From the command line, run the script using the following command for your database software:
db2 -tf createDatabase.sql
Note: If you migrated from V7.5.x and the IBM Cognos BI service was deployed in the earlier environment, you can reuse the existing database instead of creating one.
Steps 25A, 26A and 27A:
Go through all these steps in order to also migrate the WebSphere Business Monitor profile to the target IBM Business Monitor profile. Remember to include steps 16A and 20A!
Before migrating the business space, it is a good practice or even necessary to complete the steps to implement the additional configuration for Business Process Choreographer. These steps are documented in the IBM Business Process Manager product documentation as part of the post-migration activities. However, they should already be implemented at this stage.
We welcome your feedback! Share your comments below.
interior glass stair steps Mar-2013 (modified) credit: (cc) Some rights reserved by Mrodaikusek
The IBM Knowledge Center Open Beta is now live on ibm.com! The Beta will run until the end of February 2014.
You can access the latest IBM Knowledge Center at http://www.ibm.com/support/knowledgecenter/
IBM is improving your technical content experience
IBM Knowledge Center is our new technology designed to bring IBM's technical publications together in a single location, and will replace our individual IBM information centers.
In this version of the Knowledge Center, IBM simplified the user experience, improved search, and refined the overall experience with many other enhancements. You can get help for IBM Knowledge Center by clicking the question mark (Help icon) in the upper right corner of any page of the Knowledge Center. The Help icon will take you to http://www.ibm.com/support/knowledgecenter/doc/kc_help.html
Send us your feedback!
IBM would like you to provide your feedback after you have had some time to use the IBM Knowledge Center, by signing in with your IBM ID and taking a few moments to complete a survey at https://www.ibm.com/software/support/trial/cst/forms/survey.wss?id=5323
Alternatively, you can click on the Feedback button at the bottom of most pages within the IBM Knowledge center to provide IBM with your input.
Known Beta limitations
We are still:
Fine tuning IBM Knowledge Center. So you might experience some minor functional problems.
Configuring and adding content to IBM Knowledge Center. So the content you see might not be exactly what you expect.
Configuring and indexing content for search. So search results might not be exactly what you expect, or might not be in all the languages you expect.
IBM would like as many IBM clients as possible to participate. The IBM Knowledge Center team would like to thank you very much for your time and for helping us make IBM Knowledge Center a better information experience!
Modified on by Bill Wentworth
Author: Victor Paulo Alves de Almeida
The starting point for any architectural decision is the requirements whether functional or non-functional. We focus primarily on solving the client's problem. However, we have a duty to show the client what the implications are of each decision regarding the environment, administration, maintenance, migration, and resources management that are required for each solution so that the client is provided with tools to assist in decision-making. Sometimes, the client has restrictions or preconceived ideas about the product that should be addressed during the requirement mapping, analysis, and architecture definition.
The goal of this article is to discuss the role of IBM Business Monitor to monitor the IBM Business Process Manager and other sources. Thinking about some aspects of the IT infrastructure, we have some important points that we must consider when you install and configure these products. These points should be considered as you move forward so they have minimal impact to your business.
We can include the IBM Business Monitor as a part of IBM Business Process Manager or leave them separated, which means they can be in the same cell or in different cells. The term cell is a concept of distributed computing that means having many servers logically grouped and managed by a central process. This conceptual discussion of what is possible and what is right to do with the product also influences the architecture definition.
Deciding to put IBM Business Process Manager and IBM Business Monitor together implicitly implies that we are somehow more concerned with monitoring business processes from IBM Business Process Manager and no other business activities from other sources. Even though we have to monitor other sources, when the products are placed in the same cell, monitoring other sources can impact the performance of application processes. When they are placed in separate cells, the application processes are not affected by executing monitoring process or stopping monitoring servers, either by overload, maintenance, or other situations. Also, there is no impact to the application processes.
When we talk about IBM Business Monitor, we are concerned with Business Activity Monitoring, which are those activities that are available through various systems and technologies; not only activities that are related to IBM Business Process Manager. The main role of the IBM Business Monitor is to enable continuous improvement of the business processes by giving end-to-end visibility through the key performance indicators that can come from metrics available at different sources, including, but not limited to, IBM Business Process Manager.
A recurring architectural discussion we have with customers is which kind of installation approach is a better fit for them. When you correctly use IBM Business Monitor in a business context, you can get all the best of its functionality and visibility of your processes.
From a management and infrastructure complexity point-of-view, when you consider the deployment of process and monitoring applications together and stopping and starting clusters, it might be easier to have a single, centralized management console for these activities. Managing both products through a single console does not necessarily imply that IBM Business Monitor is dedicated only to IBM Business Process Manager. Both products are managed together. However, when we talk about having a single deployment environment that is shared for both products, we are implicitly saying that the primary function of the IBM Business Monitor might be to monitor process applications from IBM Business Process Manager. This statement might be different if we had separate environments for each deployment environment or different cells.
From a maintenance of the products point-of-view, such as applying patches, the fact that both products are still together implies the maintenance of both. If they were separated, applying corrections can be made without the same impact as if they were together. The same process can be used when you consider stopping a cluster. For example, if we need to stop the application cluster, it would stop the process and monitoring applications as well.
Another point is that the separation of the environments might create more complexity because the number of allocated resources needed to the solution tends to grow.
From a migration point-of-view, the environment can be difficult depending on your previous choices. For example, if you have one cell with both products together and you decide to migrate from one cell (IBM Business Process Manager plus IBM Business Monitor together) to separate cells (a IBM Business Process Manager cell and a IBM Business Monitor cell), how can you migrate process and monitoring instances from the old, combined environment to a new, separated environment?
The planning and mapping of the pros and cons based on your requirements and assumptions are essential to make the correct decision before starting the installation process.
Let's examine several points to pay attention to when determining whether to have one or two cells.
Being together (one cell):
For single point of management, only one web administrative console is used for both products and servers.
There is no need to cross cell configurations.
If you decide to create only one deployment environment in the same cell:
If you decide to create two deployment environments in the same cell:
You might need to do many extra configuration steps to get the environment working.
Only the WebSphere Deployment Manager profile (dmgr) needs to be augmented by both products.
For maintenance, at least the Deployment Manager will be affected because it has both product binaries together.
Extra steps for the virtual host configuration, context root, and REST providers must be done for each environment.
There will be only one plug-in configuration file (plugin-cfg.xml) that shares the configurations for the applications of both products.
There will be only one unique business space.
Cognos, Performance Data Warehouse, and Common Event Infrastructure (CEI) are hosted on the support cluster that requires many more resources.
There will be an IBM DB2 client on the same host of the members support cluster that is needed for creating a Cognos cube. This component must be considered for resource allocation and performance tuning of the environment.
Extensive use of native processes by Cognos can affect the performance of other applications running on the same Java virtual machine (JVM).
Migration is more complex if you have to migrate from a single to a separated cell.
Being separate (cells for each product):
You will have two points of management with two IBM Integrated Solutions Consoles.
You might need another HTTP instance for the second cell. Otherwise, you have to configure the plugin-cfg.xml file manually.
You will have two business space applications; one for each cell. If you have to use a single presentation layer for process and monitoring applications, such as WebSphere Portal Server, you will have to integrate twice. You will have to integrate once between WebSphere Portal Server and IBM Business Process Manager and once between WebSphere Portal Server and IBM Business Monitor.
Cross-cell configuration will occur between the IBM Business Monitor and the IBM business Process Manager. Both cells must use the same user registry.
The Cognos server is separate and you can tune or give more resources to it.
Maintenance can be done without interfering with the application process environment.
IBM Business Monitor can be used by different sources; not only process applications.
Migration can be done for each product separately.
What do you think?
Have you ever had this kind of discussion? Share your experience and your point of view with us by adding comments below this post.
For more information, refer to the IBM Redbooks publication entitled, IBM Business Process Manager Version 8.0 Production Topologies.
This blog was posted on May 08, 2013 by Bill Wentworth on behalf of Victor Paulo Alves De Almeida (pictured above). Victor is a WebSphere IT Specialist and is based out of Brasilia, Brazil.
Modified on by Bill Wentworth
During a residency at the IBM facility in Raleigh, NC USA, where was helping to write the IBM Redbooks publication IBM Business Process Manager V8.0 Production Topologies, I started to think about whether more is better than less.
Before I start, let me point out something about my intention: I wrote this article from a non-technical point-of-view. For sure – from a technical point-of-view – you have a lot of functions, features, and extensions that are really different in the three IBM Business Process Manager product configurations. But, because we are talking about Business Process Management, you should not look at it that much from a technical point-of-view. The main word in Business Process Management is Business! There is nothing about IT in it.
For sure “less,” which means IBM Business Process Manager Express is not really rocket science. If you want to start with a Business Process Management approach in your company, or you really want to implement only one process where not that many things are included, you can use IBM Business Process Manager Express.
More or everything?
This is the point where I have many discussions. As a lot of technical people say, “It’s just a sales and license question.” But is it really? Certainly not.
When I meet with customers, I typically hear: "We are already using the SOA approach and we have our own service layer in place. We do not want to get an additional service layer with IBM Business Process Manager Advanced. So, we are going with IBM Business Process Manager Standard.” But again, is it really just this part that determines which configuration to use? For me, no.
Other people ask themselves, ”Do we plan to integrate with another system?” When the answer is yes, the thought is that you need to use IBM Business Process Manager Advanced. Sorry, but this answer is too easy for me too. Has anyone implemented a real process without any integration or communication with another system? No. In each process, you want, or have to, integrate or communicate with another system. Otherwise, it does not make that much sense. Why do you want to automate an informal process where people still have to look for the data that they need?
For me, it can be very difficult to point out the right things and make the right decision in the end.
My opinion (and please do not hesitate to correct me if I’m wrong) is this: You can’t answer these questions in a general way. You need to analyze what is the best choice for your situation.
Some points that might help you:
Find the long term goal that you have with the Business Process Management approach
If you just want to test the Business Process Management methodology and you do not have the right people to support it, it does not make any sense to go with the biggest platform you can get. Just start and grow into it!
Analyze the processes that you want implement and determine how you want them implemented
It does not make sense to start with the largest and most important process that you have and try to implement everything in the first release. Again, just start and grow into it! If you are doing it right, you will see – your Business Process Management implementation will grow.
Analyze the landscape in which you are working
If you are working in a large company, maybe there are also important factors to consider around you.
At first, forget the money!
Analyze which systems that you want to integrate and look to the future. If you have only one system with a simple web service integration point, maybe IBM Business Process Manager Standard can fulfill your requirements.
Afterward, think in money!
Analyze the pros and cons from a budget perspective. It does not make that much sense for you buy everything. Then, afterward, you discover that you are not able to find the budget for the system or the staffing for your projects.
A very good reference on how to plan and how to start is in the IBM Redbooks publication entitled, Scaling BPM Adoption: From Project to Program with IBM Business Process Manager. You really should have a look at it.
You see – it is not just a purchasing and, for sure, it is not just a technical question. The best approach I see is to go with a Business Process Management Solution Architect to fulfill the steps and help with the decision. But be careful, I am not talking about an IT Architect. It should be a Business Process Management Solution Architect that has experience in other Business Process Management projects. The Business Process Management Solution Architect looks from a business point-of-view with one eye on the IT point-of-view.
So, how do you determine which IBM Business Process Manager product to use? I really would appreciate hearing your opinion about it. Maybe you have your own experiences, have your own view, or you can add a point that I forgot. Perhaps we will get a full list of all of the considerations. Add a comment below so we can find a better or, maybe a general answer, for this question!
Matthias Warkentin is a Business Process Management Analyst, Consultant, and Developer for the IBM Software Services for WebSphere Team. He is based in Zurich, Switzerland.
Modified on by Bill Wentworth
Posted on April 26, 2013 by Bill Wentworth on behalf of Vasfi Gucer (pictured below)
I have some great news for the IBM Business Process Manager fans!: We just published the IBM Business Process Manager Version 8.0 Production Topologies, SG24-8135 book on the ITSO web site. The book is an update of the existing book IBM Business Process Manager V7.5 Production Topologies, SG24-7976 and provides a detailed insight into implementing production topologies with IBM Business Process Manager V8.0.
During the project we had a lot of discussions on how to structure the book. We finally agreed on the following approach that we think most people would take when implementing IBM Business Process Manager.
Decide on the most suitable topology for your environment
First step for implementing the topology is probably the most difficult: Deciding on the topology! In Part 1 of the book, we present different production topologies available with IBM Business Process Manager. For example:
Clustered topology choices such as:
Single Cluster topology
Remote Messaging topology
Remote Messaging and Remote Support
Remote Messaging, Support, and Web
Advanced topology choices such as:
Cross Cell topology with IBM Business Monitor
Five cluster topology
This part covers the selection criteria for when to select a given topology, so you will be able to make an informed decision when choosing a specific topology.
Create the chosen topology using deployment environment patterns
Next step is creating the topology. In Part 2, we provide a series of step-by-step instructions for creating the production topology environments using deployment environment patterns. This includes topologies that incorporate IBM Business Monitor and advanced topology topics.
Perform the post installation steps
Part 3 covers post installation instructions for implementing the production topology environments. Depending on your topology, you need to complete one or more of these steps in your installation. The following steps are covered in this part:
Configuring IBM Business Process Manager to utilize IBM HTTP Server and WebSphere proxy server
Configuring the SMTP server
Converting offline Process Server to online
Connecting IBM Process Designer and IBM Integration Designer with Process Center
Connecting a Process Center with another Process Center
So why should you read this book? Matthias Warkentin, a Business Process Manager consultant and one of the authors of the book, answers this question on this video, which also shows the team working on the book in the Raleigh ITSO Center.
In addition to the Redbooks, as part of this project we published a new Solution Guide entitled, Improve Design and Deployment of Processes Using IBM Business Process Manager V8.0. Check out the new Redbooks and the Solution Guide and let me know what you think in the comments section below. By the way, the Redbooks publication has not been through the ITSO editing process. I expect the final version to be available by the end of May 2013. Enjoy your new Business Process Manager deliverables from ITSO!
Vasfi Gucer is an IBM Redbooks Project Leader. He works with technical experts to create books, guides, blogs, and videos. Follow @VasfiGucer on Twitter.
Planes, trains, and automobiles need to be tuned up regularly to maintain optimum performance. Scales and clocks and other devices of measurement need to be regularly calibrated for precision. Musical instruments need to be kept in tune to, well - sound good. Your business processes are not very different. Performance, precision, and a comfortable aesthetic are all important measurements of a well-defined business topology.
In the same way you know when a car needs a tune up (slow or unresponsive acceleration, decreased performance, higher fuel consumption, and so on), or a guitar is out of tune (that Spinal Tap cover you’re playing sounds even worse than the original version), you’ll notice similar symptoms arise in your business processes. IBM Business Process Manager (BPM) Standard, IBM Business Process Manager Express, and IBM Business Process Manager Advanced V8.0 and IBM Business Monitor V8.0 provide an integrated development and runtime environment based on a key set of service-oriented architecture (SOA) and business process management technologies.Here, I’ll talk about some of the basic steps you can take to ensure your Business Process Manager processes are fully optimized.
The obvious solution for remedying an out of tune guitar is to tune it, using a digital tuner or tuning it against an in-tune guitar. But, if the strings are old, or if there are problems with the neck, or the frets are worn, the guitar won’t stay in tune for long. Similarly, you can tune your business processes using the methods that have been around for so long, but if the basic structure of your business environment is compromised by underlying issues, or is simply out of date, these methods are a temporary fix at best.As an example, consider the fact that 64-bit Java virtual machines (JVM) can accommodate essentially unlimited heap sizes (assuming there is sufficient physical memory to back the heap). Now consider how new frets in addition to new strings will make your lead solos dazzlingly stellar.
An old saying in music is that the song is only as good as the instrument. You may knock off riffs as good as Jimmy Page on a dime store imitation of a Telecaster, but your audience will still groan as loudly as the users of your business processes will when they experience delays and timeouts because of outdated equipment and technology. Choosing the appropriate hardware topology for your Business Process Management environment is the key for ensuring optimal performance. Keep the following tips in mind when designing your topology:
- Deploy the appropriate hardware for your hardware configuration.
- Deploy local modules in the same server.
- Consider using a best practices approach for clustering, instead of a single server configuration.
- Evaluate service providers and external interfaces to maximize throughput capacity.
Tuning just one or two strings on a guitar will not work - all of the strings must be tuned in order for it to be playable. The same is true for your business processes. As such, here’s a quick checklist of tuning tips that cover all areas of your IBM Business Process Manager (BPM) environment:
- Use a 64-bit JVM for all servers.
- Disable tracing, logging, and monitoring when possible.
- Ensure all of your databases are well-tuned.
- If security is required, use Application security, not Java2 security.
- Use an appropriate hardware configuration for performance measurement (not notebooks or desktops).
- If hardware virtualization is used, ensure that adequate processor, memory, and I/O resources are allocated to each virtual machine.
- Minimize network latency and ensure sufficient network bandwidth between all systems in the configuration.
- Do not run production servers in development mode or with a development profile.
- Tune external service providers and external interfaces to ensure that they do not cause a system bottleneck.
- Message-driven bean (MDB) activation specifications.
- Thread pool sizes.
- Settings of data sources for connection pool size and prepared statement cache size.
- Increase the maximum number of connections in the data pool to greater than or equal to the sum of all maximum thread pool sizes.
This list represents just the fundamental requirements for optimal performance. See IBM Business Process Manager V8.0 Performance Tuning and Best Practices, REDP-4935-00 for a complete list of tuning recommendations for all areas of your IBM Business Process Manager topology.
In conclusion, while a well-crafted and perfectly tuned guitar may not be all it takes for you to quit your day job, having perfectly tuned and optimized business processes will make your day job that much more enjoyable.
On Tuesday, June 26th, Version 7.0.0 Fix Pack 5 was released for the following Business Process Management products:
The list above links to the download and installation information for each product.
We hope that your experience with this fix pack exceeds your expectations. However, there might be times when you need to contact IBM Support to resolve issues. To help expedite the support process, the following documents are available to explain the information that IBM Support needs to resolve both general and specific functional product issues:
WebSphere Business Monitor
WebSphere Enterprise Service Bus
WebSphere Integration Developer
WebSphere Process Server
Today, we are announcing an upcoming change to the Twitter accounts for the IBM Business Process Management (BPM) product family. For your convenience, and to better align with our product family strategy, we are consolidating the IBM_Lombardi, IBM_Modeler, IBM_Monitor, and IBM_ProcessServ Twitter accounts into one Twitter account. Effective Wednesday, February 1, 2012, we will consolidate these four Twitter accounts into one Twitter account called IBM_BPM. To denote product-specific tweets, we will use the following #hashtags:
- IBM Business Process Manager Standard / IBM Business Process Manager Express / IBM Business Process Manager Advanced: #bpm
- IBM Integration Designer: #iid
- WebSphere Lombardi Edition: #lombardi
- WebSphere Business Modeler: #modeler
- WebSphere Business Monitor: #monitor
- WebSphere Enterprise Service Bus: #wesb
- WebSphere Integration Developer: #wid
- WebSphere Process Server: #wps
So, what does this change mean for you?
Current IBM_ProcessServ followers
If you are currently following the IBM_ProcessServ Twitter account, an action is not necessary. The account name will change and you will follow the new account automatically.
Current IBM_Lombardi, IBM_Modeler, and IBM_Monitor followers
If you are following the IBM_Lombardi, IBM_Modeler, or IBM_Monitor Twitter accounts, new tweets will cease on Wednesday, February 1, 2012. To avoid any interruption, follow the IBM_ProcessServ account before February 1, 2012 in advance of the change or the IBM_BPM account beginning on February 1st. If you follow the IBM_ProcessServ account before February 1st, you will automatically migrate to the IBM_BPM account. Beginning February 1st, tweets that previously were sent from the IBM_Lombardi, IBM_Modeler, and IBM_Monitor Twitter accounts will originate from the IBM_BPM account.
Note: The IBM_Adapters Twitter account will remain active.
By Colleen Lhota
Good business processes enable you to anticipate shifts in the marketplace and exceed your customers' expectations, while keeping costs under control. IBM Business Process Management (BPM) V7.5 can help you discover, document, automate, and continuously improve your business processes to increase efficiency and reduce costs.
Want to learn more about BPM V7.5? IBM Education Assistant provides more than 75 videos covering the following topics:
- Overview of IBM Business Process Management V7.5
- Business Process Manager - overview, architecture, installation, migration, configuration, the development process and key application scenarios
- Integration Designer - overview, installation and testing
- Business Monitor - overview, new features, installation, administration, dashboards, models, debugging and scenarios
- Industry Packs - overview, Banking Pack, Healthcare Pack and Telecom Pack
- Business Space powered by WebSphere - overview and new features
- WebSphere Adapters - overview, new features, technology adapter enhancements and application adapter enhancements
Watch and learn today using the IBM Education Assistant videos about BPM V7.5
To set up a robust, efficient IBM Business Monitor system, we, the administrators need to conduct a thorough self-education session beforehand. The WebSphere Business Monitor Checklist, which outlines most of the implementation considerations, is a good starting point. We also need to have a comprehensive understanding of the information center (v6.2, v7, and v7.5). In addition, Frequently asked questions (FAQ) about IBM Business Monitor is another valuable resource to help us plan, deploy, and troubleshoot.
In essence, we go through installation, configuration, model development and deployment, performance tuning, and troubleshooting to successfully deploy a WebSphere Business Monitor environment.
During the installation phase, we should verify that our system and the ID that is used for product installation meets the hardware, software, and authorization requirements.
The monitor configuration phase includes successfully configuring event distribution, security, CEI, scheduler; and additional service configuration in a network deployment environment, such as failover, database connectivity, Monitor bus, and messaging engine.
Model development and deployment
When designing and developing monitor models, we might take into consideration model versioning, trigger, usage of Deliver to all instances, event group versus monitoring context, naming scheme, and model structure.
There are many aspects to be considered when we tune our system to achieve optimal performance. These aspects include (non-exclusively) event rates, model complexity, topology, and system resources.
To troubleshoot our monitor system, we can follow the checklist, which also emphasizes referring to the FAQ for common problem determination.