Part 1 of 4: Pre-migration considerations
This blog is an effort to explain some of the pre-migration considerations through post-migration steps to make the overall migration experience a sweet one. As you may be aware, migration can be very complex and time consuming. I hope this post helps you avoid some of the pitfalls.
This blog is split into the following 4 parts to keep it simple and compact:
It focuses on migrating a typical WebSphere Process Server Network Deployment v7.x golden topology on source machine to an IBM Business Process Manager Advanced v8.0 Remote Messaging, Remote Support pattern deployment environment on target machine running the same operating system as the source system. Note: These steps are applicable only if you are migrating to the remote target system. We would love to hear your feedback and appreciate you sharing your own experience with us.
- WebSphere Process Server v7.0.0 Fix Pack 4 is installed in the following path for this exercise: c:\WPS70 on source machine
- IBM Business Process Manager Advanced V8.0 is installed in the following path for this exercise: C:\BPM80 on target machine
Note: C:\BPM80 is used as a sample path in this exercise and you can change it, as appropriate, to your environment
If your applications uses WebSphere Adapters or CICS Adapters then see the Runtime premigration checklist
document on how to update the applications before you begin runtime migration procedures.
Before migrating, you need to backup the whole source environment and prepare the remote target environment. Follow these steps:
- Check the following link to ensure your database version is supported and, if need be, upgrade your database and test it out:
- Install the migration target product, IBM Business Process Manager Advanced V8.0, with required interim fixes on a separate machine running the same operating system as the source system.
For fixes, see: http://www.ibm.com/support/docview.wss?uid=swg27025131
- Create a default WebSphere Application Server profile on the system that has the new version installed and the same operating system as the source system.
Use the Profile Management Tool or the manageprofiles command on IBM Business Process Manager Advanced V8.0 machine. For example:
c:\BPM80\bin>manageprofiles -create -profileName TestAppSrv -nodeName TestNode -serverName Testserver -cellName TestCell -hostName vmwbil2w7d -winserviceCheck false -templatePath C:\BPM80\profileTemplates\default
Note: Provide the full computer name for the -hostName parameter.
Note: This profile is created to export the remote machine's details through the BPMCreateRemoteMigrationUtilities command and profile itself is not used for the IBM Business Process Manager Advanced environment.
You can delete this profile after the migration process is completed.
- Check the SystemOut.log file on the source machine (WebSphere Process Server V7.x ). If you find any unexpected errors, then resolve them before migration.
- Synchronize the nodes in case there are any changes. Click System administration > Save changes to master repository > Synchronize changes with Node
- Set the Ulimit value to 8192 on the both the source and target systems. On UNIX-based operating systems, this change helps to avoid errors during migration due to too many open files based on the size and complexity of the cell and applications.
- Set the com.ibm.ssl.enableSignerExchangePrompt property to false in the <profile home>/properties/ssl.client.props file to avoid having the WASPostUpgrade wait indefinitely for the username and password to be entered.
For details, refer to the Changing the signer auto-exchange prompt at the client topic in the information center.
- Stop the AppTarget, support, messaging, node agents, and deployment manager in that order in the source system.
- Connect to the CommonDB database schema and run the following SQL command
select count(*) from w_statement
where pred_id=(select id from w_uri where uri like '%changeSetState')
and obj_id IN (select id from w_obj_lit_string where litval IN ('DRAFT', 'PENDING' , 'APPROVED'))
If the previous SQL command returns one or more records, then run the following command
update w_statement set obj_id=(select id from w_obj_lit_string where litval='PUBLISHED')
where pred_id=(select id from w_uri where uri like '%changeSetState')
and obj_id IN (select id from w_obj_lit_string where litval IN ('DRAFT', 'PENDING' , 'APPROVED'))
- Backup the WebSphere Process Server V7.x environment
- Backup the full WebSphere Process Server V 7.x installation directory, depending on your platform. On the Windows operating system, back up the directory as a compressed (zip) file. On Unix-based operating systems, use the “tar -cvf” command to back up the directory.
- Run the backupConfig command to back up the configuration files for the deployment manager and every node. For example:
C:\WPS70\bin>backupConfig C:\WPS70\profileBackup\Dmgr.zip -profileName Dmgr01
C:\WPS70\bin>backupConfig C:\WPS70\profileBackup\Custom01.zip -profileName Custom01
- Backup the databases that are used by WebSphere Process Server and those databases that are used for the deployed applications. Backup the following databases that are configured by any of the migration source profiles according to the documentation for your databases:
Backup the .nifRegistry file. The .nifRegistry file identifies the installation root for all installed WebSphere Process Server products. It also identifies the installation root for all installed WebSphere Application Server products. It is located at the following directories:
- Business Process Choreographer Database
- Business Space database
- Common database
- Common Event Infrastructure Database
- Messaging Engine Database
Note: Back up the database and transaction logs ( step 13 ) at the same time to keep transaction logs synchronized with the database.
Take a backup of source tranlog and Partnerlog files. They are located in the <Install Root>/profiles/<profile name>/tranlog directory.
- Linux/UNIX-based operating systems: /opt/.ibm/.nif/.nifregistry
- Windows operating systems: C:\Windows\.nifregistry
Create the remote migration utilities image. Run the BPMCreateRemoteMigrationUtilities command on the target system to create an archive file. The file contains all the commands and their prerequisites that need to be invoked on the system containing the source profile to be migrated. For example: c:\BPM80\bin>BPMCreateRemoteMigrationUtilities remoteMigrationUtilities.zip
Note: By default, the remoteMigrationUtilities.zip file is created in the <Install Root>/util/migration directory.
Copy the remote migration utilities ( remoteMigrationUtilities.zip file from step 14 ) from the target system to the source system. Then, extract the remote migration utilities on the source system into their own unique directory. For example:
Copy C:\BPM80\util\migrationremoteMigrationUtilities.zip to C:\WPS70\migration80
Extract C:\WPS70\migration80\remoteMigrationUtilities.zip to C:\WPS70\migration80\util
Continue to Part 2.
Every quarter the Knowledge Engineering team puts together a
list of high-value content, most requested documents, and links that we think
will help you in answering your questions related to the BPM products, and we call
these our “featured documents”.
These “featured documents” often include the latest updates
to the different BPM products, documents that have been proven useful in
solving technical issues in the past, important alerts that we think you should
be aware of, and some of the highest accessed links that many of our customers
have found helpful to them.
The “featured documents” are divided into three main
sections to help you find the content you need even faster:
In the spotlight: High-value content, alerts and updates for
your BPM product
Plan: Information that helps you plan and manage your BPM
Education: Useful resources to further hone your skills in your BPM product
So head over to the featured documents for your BPM products
below, and start digging away at the articles!
By Sharath Srinivas, IBM Business Process Manager L2 Support.
Updated: September 7, 2012
This blog entry walks you thru the step-by-step procedure to create a stand-alone Process Center server and a Remote Messaging, Remote Support and Web pattern-based network deployment environment for the Process Server. Setting this environment can be accomplished in many different ways and this blog post approaches the task in a simple, yet commonly used, methodology that is applicable for most platforms. We would love to hear your feedback and would appreciate it if you shared your own experience with us.
This blog is split into the following 3 parts:
Complete the following steps:
- Ensure that the following prerequisite configuration exists for the base system to follow this exercise:
IBM Business Process Manager Version 8.0 is installed in the following directory: E:\IBM\bpm80
Note: E:\IBM\bpm80 is used as a sample path in this exercise. You can change it appropriately for your environment.
- Create a response file to use for the manageprofiles command. Here is a sample response file used to create stand alone Process Center profile configured against DB2.
Note: dbUserId=BPMUSER is the user ID for all of the Business Process Manager databases if the specific user IDs are not provided for each component database.
- Run the manageprofiles command from the E:\IBM\bpm80\bin directory. For example:
E:\IBM\bpm80\bin>manageprofiles -response E:\IBM\bpm80\BPM\samples\manageprofiles\PCStd_StandAlone_DB2.response
- Check the E:\IBM\bpm80\logs\manageprofiles\<Profile_Name>_create.log file for INSTCONFSUCCESS. If you see INSTCONFFAILED, search for SEVERE or error.
- Complete these database activities:
Note: SQL scripts are generated in the E:\IBM\bpm80\profiles\<profile_name>\dbscripts\ directory.
Important: If the IBM Business Process Manager database user ID ( BPMUSER ) has the administrator privileges then complete the steps in section 5.1. If not, then follow the steps in section 5.2.
Follow these commands:
b. db2 ATTACH to DB2 user BPMUSER using <password>
Note: DB2 is the default instance name, change if your database instance name is different
c. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\ProcessServer\DB2\PC_BPMDB\createDatabase.sql
Note: Profile name - ProcCtr , Database Name - PC_BPMDB
d. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\PerformanceDW\DB2\PC_PDWDB\createDatabase.sql
e. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\BusinessSpace\Node01_ProcCtrServer\DB2\PC_CMNDB\createDatabase.sql
f. db2 connect to PC_BPMDB user BPMUSER using <Password>
g. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\ProcessServer\DB2\PC_BPMDB\createTable_ProcessServer.sql
h. db2 -tdGO -vf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\ProcessServer\DB2\PC_BPMDB\createProcedure_ProcessServer.sql
i. db2 connect to PC_PDWDB user BPMUSER using <Password>
j. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\PerformanceDW\DB2\PC_PDWDB\createTable_PerformanceDW.sql
k. db2 connect to PC_CMNDB user BPMUSER using <Password>
l. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\BusinessSpace\Node01_ProcCtrServer\DB2\PC_CMNDB\createTable_BusinessSpace.sql
Go to step 6
Important: If the Business Process Manager database user ID ( BPMUSER) does not have administrator privilege, then follow these steps:
a. Generate the SQL scripts for messaging engines and run the sibDDLGenerator command from E:\IBM\bpm80\bin directory.
E:\IBM\bpm80\bin>sibDDLGenerator -system db2 -platform windows -schema MEDPS00 -user BPMUSER > E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB\ProcessServer_ME.sql
E:\IBM\bpm80\bin>sibDDLGenerator -system db2 -platform windows -schema MEDPE00 -user BPMUSER > E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB\PerformanceDW_ME.sql
Note: The MEDPS00 and MEDPE00 schema names that are used for ProcessServer and PerformanceDW respectively are default names and should not be changed unless you use a DbDesignGenerator command to generate dbDesign file and plan to use it while creating profile. Output files are created in the E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB directory as redirected in the previous command.
c. db2 ATTACH to DB2 user db2admin using <Password>
Note: The db2admin user needs to have administrator privilege.
d. db2 create database PC_BPMDB automatic storage yes using codeset UTF-8 territory US pagesize 32768
db2 UPDATE DB CFG FOR PC_BPMDB USING LOGFILSIZ 4096 DEFERRED
db2 UPDATE DB CFG FOR PC_BPMDB USING LOGSECOND 64 DEFERRED
Note: SQL commands in step (d) are available in <install Root>/profiles/dbscripts/<ProcessServer or PerformanceDW or BusinessSpace >/<databse type>/createDatabase.sql
e. Repeat step (d) for other two databases PC_PDWDB and PC_CMNDB
f. db2 connect to PC_BPMDB user db2admin using <Password>
g. db2 Grant CREATETAB on database to user BPMUSER
h. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB\ProcessServer_ME.sql
Note: Messaging engine database objects script generated in step (a), use PerformanceDW_ME.sql for PC_PDWDB
i. Repeat steps (f,g and h) for PC_PDWDB and steps ( f and g ) for PC_CMNDB
j. db2 connect to PC_BPMDB user BPMUSER using <Password>
k. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\ProcessServer\DB2\PC_BPMDB\createTable_ProcessServer.sql
l. db2 -tdGO -vf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\ProcessServer\DB2\PC_BPMDB\createProcedure_ProcessServer.sql
m. db2 connect to PC_PDWDB user BPMUSER using <Password>
n. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\PerformanceDW\DB2\PC_PDWDB\createTable_PerformanceDW.sql
o. db2 connect to PC_CMNDB user BPMUSER using <Password>
p. db2 -tvf E:\IBM\bpm80\profiles\ProcCtr\dbscripts\BusinessSpace\Node01_ProcCtrServer\DB2\PC_CMNDB\createTable_BusinessSpace.sql
- Run the bootstrapProcessServerData command from the profile\bin directory. For example:
E:\IBM\bpm80\profiles\ProcCtr\bin>bootstrapProcessServerData -dbJDBCClasspath E:\IBM\bpm80\jdbcdrivers\DB2
- Check the E:\IBM\bpm80\profiles\ProcCtr\logs\bootstrapProcesServerData.<time_stamp>.log file for any errors.
- Start the Process Center server. For example:
- Check the E:\IBM\bpm80\profiles\ProcCtr\logs\ProcCtrServer\SystemOut.logand startServer.log files for any errors.
- Check the E:\IBM\bpm80\profiles\ProcCtr\logs\AboutThisProfile.txt file for detail and port information.
- Log in using the default port numbers. For example:
See Part 2 of 3
By Sharath Srinivas, IBM Business Process Manager L2 Support.
This blog is split into the following 3 parts:
For this exercise, the deployment manager and the custom nodes are set up on the same system that is used for Process Center. Change them appropriately for your environment.
- Create a response file, which is used by the manageprofiles command, for the deployment manager. Here is a sample response file:
Note: PS_CMNDB is the database name for the Process Server CommonDB
- Run the manageprofiles command from the E:\IBM\bpm80\bin directory.
E:\IBM\bpm80\bin>manageprofiles -response E:\IBM\bpm80\BPM\samples\manageprofiles\PSStd_Dmgr_DB2_DATASERVER.response
- Check the E:\IBM\bpm80\logs\manageprofiles\Dmgr01_create.log file -- Profile name - Dmgr01
Check for INSTCONFSUCCESS. If you see INSTCONFFAILED, search for SEVERE / error
- Start the deployment manager. For example:
- Check the following log files:
- Create a custom profile response file. Here is a sample response file:
- Run manageprofiles command from E:\IBM\bpm80\bin directory. For example:
E:\IBM\bpm80\bin>manageprofiles -response E:\IBM\bpm80\BPM\samples\manageprofiles\PSStd_Custom.response
Note: The deployment manager needs to be started and running.
- Check for the following message in E:\IBM\bpm80\logs\manageprofiles\Custom01_create.log file.
ADMU0003I: Node customNode has been successfully federated.
- Log on to https://localhost:9044/ibm/console/logon.jsp
- Check System administration > Nodes and make sure that the new custom node is federated.
Note: Follow steps 6 to 8 for additional custom nodes.
- Verify that custom nodes are synchronized. In the administrative console, click System administration > Nodes.
See Part 3 of 3
Source: Nalini Mohan, IBM Business Process Management Information Development
In response to customer feedback, the IBM Business Process Manager Version 8.0 Information Center has a new feature for users who prefer to have customized information specific to the configuration of the Business Process Manager product that they are planning to install. The new Interactive Installation and Configuration Guide feature offers you the ability to select:
- The Business Process Management Standard, IBM Business Process Manager Express, or IBM Business Process Manager Advanced product offering
- Your preferred database
- Your operating system
- The level of user (Administrator or non-administrator)
- The type of installation
- The type of profile.
These options are available as radio buttons in response to multiple choice questions. By submitting answers to these questions, you can generate a custom set of installation and configuration instructions for common stand-alone and network deployment environments. The following screen shot shows the new Interactive Installation and Configuration Guide, which is available at http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/topic/com.ibm.wbpm.imuc.doc/topics/bpm_roadmap_form.jsp
Comments about this new feature as well as the content of the blog are welcome.
Information centers are a great way to learn about your IBM products. They offer a powerful and intuitive interface for browsing and finding technical information on the products that you use and maintain; how to plan for and prepare your environment for the product, installation and migration, administration and the securing of the environment, samples and scenarios, troubleshooting and support - the list goes on and on. You also have the option to access these information centers online or by saving copies to your local system.
But the focus of this article is not the information centers themselves, but the technology behind them - the IBM Eclipse Help System (IEHS).
The latest version of the IBM Eclipse Help System (IEHS) contains changes that include more features and additional fixes. It is highly recommended that you upgrade if you are using a local version of the information center for the following products:
- IBM Business Process Manager
- WebSphere Business Monitor/IBM Business Monitor
- WebSphere Business Compass
- WebSphere Process Server
- WebSphere Enterprise Service Bus
Version 7.5.1 product releases:
Version 7.5 product releases:Version 7.0 product releases: Version 6.2 product releases:Version 6.1.2 product releases:
The WebSphere Support Technical Exchange (WSTE) program is a great way for you to learn about popular support topics and questions that come into the IBM support center. Hosted virtually over conference calls and web conferences, the WSTE team organizes a number of technical sessions each month on a variety of products: WebSphere Adapters, WebSphere Business Monitor, IBM Integration Designer, IBM Business Process Manager, WebSphere Process Server, just to name a few. There’s also a chance at the end of each session for you to interact with the BPM subject matter experts from IBM. All WSTE sessions are recorded and are generally made available on the website within one to two business days after the presentation.
There’s no fee to participate in a WSTE, and no registration is required.
So why wait! Head over to the WebSphere Support Technical Exchange page and see what the WSTE team has prepared for you.
If there is a particular BPM topic you’d like to see in an upcoming WSTE, you can also send your feedback to the WSTE team at email@example.com. We do read every single piece of mail you send!
Finally here are a few of my favorite BPM WSTEs in 2012 that you might also find helpful:
By Daniel Julin
We are happy to announce the availability of the first full beta release of IBM Support Assistant 5.0. You can find a more complete description, download and installation instructions at http://www.ibm.com/support/docview.wss?uid=swg27024922.
Many thousands of you have been using IBM Support Assistant 4.x over the last several years, to help streamline various troubleshooting tasks such as collecting diagnostic data and analyzing that data using a library of problem determination tools.
One of the limitations of IBM Support Assistant 4.x is that it requires the installation of a special application on each user's desktop, and it does not allow for easy sharing of resources, files and tools among multiple users.
With IBM Support Assistant 5.0, we want to address these concerns by adopting a cloud-based approach. IBM Support Assistant 5.0 is structured as a web application running in WebSphere Application Server. Multiple clients can connect to the application remotely, through their browser. Of course, you can also install the whole system locally, and use it as a private desktop application if you prefer.
In addition to providing this new cloud-based architecture, we anticipate that IBM Support Assistant 5.0 will serve as a solid foundation for the future evolution of troubleshooting tools and services within the IBM software family. We look forward to providing many new useful functions, through future updates to this initial Beta.
Please try this out, and send us feedback through this blog, through the Feedback link in the application itself, or by speaking with your IBM Support representative.
Over the past few weeks, I've seen multiple questions related to the DateTime field and time zones with WebSphere Process Server. The question is why does the timezone get normalized in WebSphere Process Server?
The DateTime field in the original message is usually a local timezone set as: <DueDate>2012-03-06T09:43:54.167-06:00</DueDate>
However, after the data passes through WebSphere Process Server, the time is normalized to UTC/GMT/Zulu time. For example: <DueDate>2012-03-06T15:43:54.167Z</DueDate>
The answer to the question is that the XML functionality and XML components that WebSphere Process Server provide, use the convention to always normalize the datetimes value to the UTC/GMT/ZULU timezone. WebSphere Process Server does not provide options to configure specific timezones for its output. The following document describes this issue: http://www.ibm.com/support/docview.wss?uid=swg21503646
Note:: Although the document is written for web services, the same general principles apply to other situations with XML output.
The key point to remember is that the serialization that WebSphere Process Server uses is one of many possible XML messages. However, the value it has chosen is valid and conforms to XML specifications. So, if your destination service conforms to the full XML apecifications, it should be able to understand and treat the DateTime field exactly the same no matter if it is provided in UTC or a local time zone format.
From a logical point of view, any of the time zones still represent the same point in time. It is the same situation as why the numbers "1.0", "1.00" , and "01.0" are all equal in XML.
There are an infinite number of different possible options that you might want related to the format of the XML message, which is beyond the scope of what can be reasonably provided by the product. As other example, we have run across requests for WebSphere Process Server to customize
- The namespace prefixes chosen
- The order of namespace declarations
- The white space tabbing.
Each of these requests for customizations actually reveal a deficiency in the consuming service not being able to fully understand the XML specification and logically equivalent XML messages. Because there are an infinite amount of options, an architectural decision was made to not provide these customization options, but only ensure that we will provide a message that is valid and logically equivalent.
If customization of the message is desired in a specific format, you can use custom code to modify or adjust the message using a custom DataHandler, WebServiceHandler, or other exit point, where you can work with the XML string directly.
Another option is to declare the field as a string, then the value is not normalized to the UTC time zone. Then, you can use the Java Datetime API with the Java String API to produce the desired format.
It is not an uncommon occurrence to run into problems when trying to discover a WSDL using the Web Service Integration component from within the Process Designer tooling. These scenarios can happen for a variety of reasons, ranging from the wrong URL being used to actual problems in the structure of the WSDL or associated XSD files. The problem is that from Process Designer, the only error reported is a pop up box that looks like this:
This error does not help too much to point out the actual core problem. All is not lost, though. While Process Designer currently does not give a detailed message, Process Center does. It should be noted that when doing the WSDL discovery, it is actually done from the Process Center side. So even though you are using Process Designer, it is the connected Process Center that has the actual detailed log files. If you experience a problem with WSDL discovery, the best place to check is the SystemOut.log file, which is located in the Process Center's profile logs directory. In most cases, the resulting error will directly point to the problem and it can be remedied.
||Video: Installing WebSphere Process Server V7.0.0 Fix Pack 4
Need help installing WebSphere Process Server V7.0.0 Fix Pack 4? Watch this step-by-step demonstration video, created by the IBM Support team and now available on IBM Education Assistant!
This 6-minute video demonstrates the five steps required to silently install WebSphere Process Server V7.0.0 Fix Pack 4 without an internet connection:
- Install WebSphere Application Server.
- Install Update Installer (UPDI).
- Uninstall two Interim Fixes (SDKPM00452 and PK98944) that come with the WebSphere Application Server installation.
- Install Installation Manager V1.5.
- Install WebSphere Process Server V7.0.0 Fix Pack 4 using a customized response file.
A Readme file is also provided that contains the following helpful information:
- Links to the install packages that you will need to download
- The commands that are used in the video and so you can copy and paste
- Links to the response files used in the video
Want to learn more? IBM Education Assistant offers over 100 videos about Business Process Management V7.0!
I recently published two new technotes related to some common issues that I have encountered in Support. Both of these issues are common issues that multiple IBM WebSphere Process Server users have come across. If you are encountering delays with WebSphere Process Server start-up, or WS-AT headers in your web services, then these publications might help you solve your problem. Check them out!
WebSphere Support Technical Exchange (WSTE) has recently posted a replay broadcast session on Using Headless Build ANT Script to Generate Deployable EAR File for Server Deployment. The purpose of this session is to educate users to build, generate, and deploy artifacts from the command line using both WebSphere Integration Developer and serviceDeploy. It introduces two fundamental approaches to build and deploy modules using Ant, using headless in WebSphere Integration Developer, and using serviceDeploy in WebSphere Process Server. It further discusses in details the pros and cons of choosing one of the approaches over the other. The session covers recommended practices in automated builds, common user errors, and resolving problems that you might encounter.
The IBM Business Manager suite is a comprehensive BPM platform providing users the visibility and insight to manage business processes. Version 7.5 is the latest release of the suite, which ranges from development tools and production servers. With this release, application development and deployment are more scalable, agile, and on demand.
To help users master the new products, product training materials are provide in a variety of online or in-class forms. For example, the IBM Integration Designer V7.5 - Installation and Related Topics
is an online training session offered by WebSphere Support Technical Exchange. The session focuses on IBM Integration Designer installation, a development tool of the IBM Business Manager suite. The discussion contains an overview on the installation, step-by-step walk-through of two typical installation scenarios, installation with product launchpad and silent installation. The FAQ section contains answers to commonly asked questions, such as, system requirements, database requirements, process center and process server test environment installation and configuration, security, coexistence, non-admin user, and Business Space issues. The FAQ section is followed by a troubleshooting discussion about basic techniques used in troubleshooting a failed installation. The session ends with a recommendation section, which contains best practices to avoid potential installation failure.
This post represents the first, in what we hope, will be a series of question and answer blogs with developmental, architectural, and project management experts for the IBM Business Process Management family of products.
As a 10-year IBMer writing technical documentation and providing technical support, I am frequently reminded of the need to look at our products with a customer-centric lens. With that focus, I strive to understand how you use our products and what kind of information truly helps you solve business issues. So, with that perspective in mind, I wanted to focus on the differences that you might encounter as you move from WebSphere Lombardi Edition Versions 7.x and 6.x to IBM Business Process Manager Standard, IBM Business Process Manager Express, or IBM Business Process Manager Advanced Version 7.5. (From this point forward, these products will be collective referred to as the IBM Business Process Manager products.) To gain an understanding of the differences, I had a discussion with Zachary Roadhouse, who is the Chief Engineer for the WebSphere Lombardi Edition and IBM Business Process Manager Standard products. The following information is based on that discussion:
Q: Can you upgrade from Lombardi Teamworks Version 6.1.x and 6.2.x?
A: With the introduction of the IBM Business Process Manager Version 7.5 products, upgrades are now available for the Lombardi Teamworks Version 6.x product. Previously, an upgrade path was not available for this product. An upgrade from Lombardi Teamworks Version 6.2.x and 6.1.x to the IBM Business Process Manager products enables you to have a repository-based environment for the first time. For more information on this repository-based environment, see Asset repository in the IBM Business Process Manager Information Center.
If you want to upgrade from Lombardi Teamworks Versions 6.1.x and 6.2.x directly to IBM Business Process Manager Version 7.5.0 Fix Pack 1, you must upgrade to IBM Business Process Manager Version 7.5 and then upgrade to Fix Pack 1. Otherwise, you might encounter the following error message:
Target database schema version: 7.5.0 is not in the supported list of versions to upgrade [7.5]
Q: What are the similarities and enhancements between Lombardi Teamworks / WebSphere Lombardi Edition Version 7.x and the IBM Business Process Manager Version 7.5 products?
A: IBM Business Process Manager Standard uses the same functional footprint and code base that you are accustomed to using with Lombardi Teamworks / WebSphere Lombardi Edition Version 7.x. However, the new products contain enhancements that aid in installation and configuration. Let us focus on just a few of the enhancements in Version 7.5:
- Uses the IBM Installation Manager, which is a common installation mechanism across some of the WebSphere-branded products and is new to you if you are familiar with the installation process for Lombardi Teamworks V6.x, Teamworks V7.x or WebSphere Lombardi Edition V7.x. IBM Installation Manager is a wizard-based user interface that enables you to install the product and update both Process Designer and IBM Integration Designer. However, before you upgrade to the latest fix pack using Installation Manager, see the following documents:
- Provides full support for creating and configuring profiles using the Profile Management Tool. For more information, see Starting the Profile Management Tool.
- Provides wizard support through the administrative console to create sophisticated configurations such as clusters. For more information, see Creating a cluster.
Q: What are some of the differences between the Standard, Express, and Advanced versions of IBM Business Process Manager V7.5?
A: Although there are many differences between these products, here are some notable differences:
- IBM Business Process Manager Express has a limited license for the Process Center and Process Server. Also, it does not offer cluster support. However, IBM Business Process Manager Standard provides clustering support.
- IBM Business Process Manager Advanced includes the functionality that was present in WebSphere Lombardi Edition Version 7.x and now, in IBM Process Designer, includes Advanced Integration Service. Advanced Integration Service allows the Process Designer author to access BPEL, complex web services, mediation flows, and SCA components that you create using the IBM Integration Designer. The Advanced Integration Service allows for more advanced integration capabilities than in the standard or express products.
- IBM Business Process Manager Standard and IBM Business Process Manager Express target a process developer with the following knowledge:
- Understands business requirements and can create the process diagram and build the user interface to enable the implementation of those requirement
- IBM Business Process Manager Advanced includes an additional role, which targets both a process developer and an integration developer. The integration developer should know Java and be a service-oriented architecture (SOA) expert in a technology such as web services. The integration developer will use IBM Integration Designer to implement the business process requirements.
- IBM Business Process Manager Advanced enables an integration designer to author assets in IBM Integration Designer and publish those assets to the process center; you do not need to manually develop the assets. The product infrastructure configures and installs the web application (WAR) or enterprise archive (EAR) file automatically; you do not need to manually deploy the asset. The tooling assembles the asset due to the existence of versioning and life cycle support.
- IBM Business Process Manager Advanced comes with WebSphere Enterprise Service Bus, Business Process Execution Language (BPEL), and Service Component Architecture (SCA) technology.