Professional Documents
Culture Documents
Version 8.0
April 2010
Copyright
& Docu-
ment ID
This document applies to webMethods Product Suite Version 8.0 and to all subsequent releases.
Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions.
Copyright © 2008-2010 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or
their licensors.
The name Software AG, webMethods, and all Software AG product names are either trademarks or registered trademarks of Software AG
and/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks of their
respective owners.
Use of this software is subject to adherence to Software AG’s licensing conditions and terms. These terms are part of the product
documentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).
This software may include portions of third-party products. For third-party copyright notices and license terms, please refer to "License
Texts, Copyright Notices and Disclaimers of Third Party Products." This document is part of the product documentation, located at
http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).
This guide is for users who are upgrading to the latest webMethods 8.0 product releases.
Document Conventions
Convention Description
Bold Identifies elements on a user interface.
Narrow font Identifies storage locations for services on webMethods Integration
Server, using the convention folder.subfolder:service.
UPPERCASE Identifies keyboard keys. Keys you must press simultaneously are
joined with a plus sign (+).
Italic Identifies variables for which you must supply values specific to your
own situation or environment. Identifies new terms the first time they
occur in the text.
Monospace Identifies text you must type or messages displayed by the system.
font
{} Indicates a set of choices from which you must choose one. Type only
the information inside the curly braces. Do not type the { } symbols.
| Separates two mutually exclusive choices in a syntax line. Type one of
these choices. Do not type the | symbol.
[] Indicates one or more options. Type only the information inside the
square brackets. Do not type the [ ] symbols.
... Indicates that you can type multiple options of the same type. Type
only the information. Do not type the ellipsis (...).
Documentation Installation
You can download the product documentation using the Software AG Installer.
Depending on the release of the webMethods product suite, the location of the
downloaded documentation will be as shown in the table below.
Online Information
You can find additional information about Software AG products at the locations listed
below.
Note: The Empower Product Support Web site and the Software AG Documentation
Web site replace Software AG ServLine24 and webMethods Advantage.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Migrate My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Overview
This upgrade procedure explains how to install the latest webMethods 8.0 product
releases over webMethods 7.1.2, 7.1.3, 7.2, or 7.2.1 products. For some products, you must
perform additional tasks to complete the upgrade or to migrate data. This chapter
provides instructions for those tasks.
Note: This procedure does not explain how to upgrade from CentraSite 7.x to
CentraSite 8.0 SP3. If you need to perform that upgrade, contact Software AG Global
Consulting Services. CentraSite should be upgraded before any other product.
Important! Because many products share files, you must upgrade all products that are
in the same installation directory.
You must upgrade products and migrate data in the order the instructions are
presented in this chapter.
Software AG strongly recommends that you upgrade and migrate in a controlled test
environment and test that environment for proper operation before upgrading and
migrating your production environments.
Important! If you installed language packs on your 7.x products, you cannot overinstall
until those language packs are available for your 8.0 products. Then, for each affected
product, you must install the 8.0 product and the 8.0 language pack over the 7.x
product and 7.x language pack at the same time; you cannot install the 8.0 product at
one time, and the 8.0 language pack at another time. For language pack availability,
see the Globalization section of the Software AG Empower Web site.
1 Shut down the products listed below if they are running on the machine on which
you are going to overinstall.
The instructions in the table are for Windows systems. On UNIX systems, use the
instructions provided in the product documentation.
2 Shut down all other applications that are running on the machine on which you are
going to overinstall.
1 If you are upgrading webMethods Broker, back up the JMS objects and data in each
webMethods Broker installation.
2 Back up the entire 7.x webMethods installation directory.
If you have a cluster of Integration Servers, back up the installation for each
Integration Server in the cluster.
Important! For My webMethods Server, you must back up the 7.x webMethods
installation directory and the MywebMethodsServer database component at the
same time. The two must be in sync, or you will experience problems. The same is
true for Optimize and the Optimize database components.
3 Back up all 7.x databases. For instructions, see your RDBMS vendor documentation.
4 If you are going to upgrade My webMethods Server, go to the
7.x_installation_directory\MWS\server\server_instance\deploy directory and delete
all .xml files.
On the Software AG Installer’s product selection tree, existing products are shown in
gray followed by the word “Installed” (wizard mode) or the letter “I” (console mode).
Select the 8.0 products to install; be sure to select all necessary components of each
product (see Software AG Installation Guide 8.0, Typical Development Installations for
guidance).
If you are installing a product that uses an RDBMS, select Database Configuration.
You can also select new 8.0 products and optional items such as Documentation.
Note: Do not choose to install CentraSite 8.0 SP3. If you need to upgrade from
CentraSite 7.x to CentraSite 8.0 SP3, contact Software AG Global Consulting
Services.
When the installer asks for product configuration information, do the following:
Product Action
Optimize Provide the product configuration information as instructed in
Infrastructure Software AG Installation Guide 8.0.
Data Collector
Integration Provide the license file.
Server
Indicate whether you want the installer to migrate Integration
Server data.
Choose to have the installer migrate the data if you want
the installer to automatically run the Integration Server
Migration Utility with default values. The default values
migrate all port, remote server alias, and Integration
Server certificate settings; Web service endpoint aliases;
proxy settings; and the Integration Server embedded
database.
Choose to not have the installer migrate the data if you
want to specify custom migration values (for example,
migrate certain ports only), or if you want to export
migration values so you can run the migration utility
silently on other machines. In this case, you would run the
utility after installation using the instructions in “Migrate
Integration Server Data” on page 21.
webMethods Provide the license file.
Broker
My webMethods Indicate whether you want the installer to automatically
Server upgrade My webMethods Server server instances. If you do
not, you must upgrade them manually one at a time after
installation.
If you selected 8.0 products that are not yet installed on your machine, see
Software AG Installation Guide 8.0 for instructions on providing the required product
configuration information.
If you installed a language pack for a 7.x product, you must overinstall the same
language pack for the 8.0 product.
Important! For each affected product, you must install the 8.0 product and the 8.0
language pack over the 7.x product and 7.x language pack at the same time. You
cannot install the 8.0 product at one time, and the 8.0 language pack at another
time.
If you had the installer automatically migrate Integration Server data or upgrade My
webMethods Server server instances, details of the migration or upgrade are written
to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. If
you are using the installer wizard (as opposed to console mode), the installer’s Finish
panel provides a link to the file.
If you installed new 8.0 products, create any necessary database components. For
detailed information and instructions, see Software AG Installation Guide 8.0.
If you installed on a Windows system, manually remove 7.x entries from the Start
menu.
Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service
configured for ;AlternateServers=(server:{1521|port};,…)
;ConnectionRetry=value; ConnectionDelay=value
RAC
;LoadBalancing=value[;option=value …]
For DB2, if the product will connect to a schema other than the
default schema for the specified database user, you must specify
these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT
PATH=current_path,schema"
Overview
This section explains how to use the Integration Server Migration Utility to migrate your
Integration Server 7.x data. You have several options, as described below.
You can run a custom migration, in which you choose which data to migrate. The
utility gathers your choices through a series of prompts, then migrates the specified
data. To run a custom migration, follow the steps below, in this section.
If you are performing migrations for multiple, identical, clustered Integration Servers
running on different machines, you can run a custom migration, export your choices
to file, and import the choices when you run the utility on other machines.
To run a custom migration and export your choices to file, follow the steps below, in
this section.
To run a migration with imported choices and a confirmation prompt before the
migration actually begins, follow the steps below, in this section. To run a migration
with imported choices silently (that is, with no confirmation prompt), see “Run the
Migration Utility Silently with Imported Settings” on page 25.
During actual migrations, if migration of a piece of data fails (for example, certificate
settings for a port), the utility asks whether to continue with the next piece of data or
abort the migration. If you choose to abort, the utility exits. It does not revert the
Integration Server 8.0 installation. You can address the issue and run the utility again.
The migration utility writes details of the migration to the migrationLog.txt file in the
8.0_installation_directory\install\logs directory. By default, the utility writes INFO,
ERROR, and FATAL messages to the log. If you want to increase the logging level to
DEBUG, go to the Integration Server_8.0_directory\bin\migrate directory, open the file
log4j.properties file in a text editor, set the log4j.logger.Migration property to DEBUG,
MigrationFile, and save and close the file.
3 The utility asks whether to migrate port certificate settings to the keystores used in 8.0
SP1. You can migrate all of the settings (enter A), none of the settings (enter N), or
selected settings only (enter S). If you enter S, the utility lists each port and asks
whether to migrate its certificate settings.
For each SSL port you migrate, the utility will convert certificate settings into the
keystores used in 8.0 SP1. If conversion fails, the utility will revert all migration
changes it made to the port and disable the port in Integration Server 8.0 SP1.
Note: If you do not migrate certificate settings for a port, and a default Integration
Server keystore exists in the 8.0 SP1 installation, the port will default to that key-
store.
4 The utility asks whether to migrate remote server alias certificate settings. You can
migrate all of the settings (enter A), none of the settings (enter N), or selected settings
only (enter S). If you enter S, the utility lists each remote server alias and asks whether
to migrate its certificate settings.
For remote server alias you migrate, the utility will convert certificate settings to the
8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it
made to the remote server alias in Integration Server 8.0 SP1.
5 The utility asks whether to migrate Web service endpoint aliases. You can migrate all
of the aliases (enter A), none of the aliases (enter N), or selected aliases only (enter S).
If you enter S, the utility lists each Web service endpoint alias and asks whether to
migrate it.
For each alias you migrate that is in use by a WSD, the utility detects the type and
transport of the WSD and copies that information to the 8.0 SP1 files. If an alias is not
in use by a WSD, the utility copies the type and transport information in such a way
that the alias is available to all WSDs, regardless of type or transport.
The utility will convert type and transport information for Web service endpoint
aliases to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration
changes it made for the alias in Integration Server 8.0 SP1.
6 The utility asks whether to migrate Integration Server certificate settings. If you enter
Y, the utility will convert the certificate settings into the keystores used in 8.0 SP1.
7 The utility asks whether to migrate proxy settings. If you enter Y, the utility will
convert your proxy settings to the 8.0 SP1 format.
8 If Integration Server 7.x used the embedded database, the utility asks whether to
migrate it. If you enter Y, the utility will copy the database tables from Integration
Server 7.x to Integration Server 8.0 SP1 and convert the tables to the 8.0 SP1 format.
Note: If you do not migrate the embedded database now, Integration Server 8.0
SP1 will create the embedded database automatically on startup but not migrate
any data to it.
9 The utility asks whether to export the migration settings from this session. If you
enter Y, the utility stores the migration settings in a file named migrate.dat in the
directory from which you are running the utility.
10 The utility asks whether to begin migration. If you want the utility to exit without
migrating any data, enter N. If you want the utility to migrate data based on the
settings you specified, enter Y; the utility prints progress messages to the command
window and the migration log. If migration completes successfully, the utility does
the following:
Deletes 7.x configuration files that are no longer used by Integration Server 8.0
SP1.
Deletes 7.x properties that are no longer used by Integration Server 8.0 SP1 from
the 8.0 SP1 configuration files, and merges the Integration Server port.cnf and
listeners.cnf file.
If Integration Server 7.x was part of a cluster, upgrades your clustering
configuration to the 8.0 SP1 format.
Update WSDLs
In Integration Server Administrator, go to the Settings > Extended page. If you have the
extended setting watt.server.xml.ncname.encode.backward.compatibility and it is set to
true, reset it to false. Then regenerate the clients for all Provider Web services that have
an operation with field names starting with "xml" in the input signature, output
signature, header, or faults.
4 If you have a cluster of My webMethods Servers, delete the 7.x cluster nodes you
have not upgraded and then add 8.0 nodes. For instructions, see Administering My
webMethods Server 8.0.
5 My webMethods Server 7.x used Jetty 5.0 as its Web server; My webMethods Server
8.0 uses Jetty 6.0. If you modified the jetty.xml file in your 7.x installation, use the
mws.{bat|sh} getconfig jetty.xml and mws.{bat|sh} putconfig jetty.xml commands to
similarly modify your 8.0 jetty.xml file.
6 Restart My webMethods Server 8.0 and open My webMethods.
2 Task applications in webMethods 8.0 have new functional privileges that relate to the
new 8.0 collaboration processes feature. Even though these privileges are displayed in
Permissions Management, you must add these privileges to the task application in
case you want to modify them later. To add the privileges to your task applications,
start Designer 8.0, go to the Import > Software AG > Existing CAF Projects Into Workspace
page, and import the task applications into Designer 8.0 using the Import button in the
Solutions View toolbar. The import process automatically checks and adds missing
task privileges. Then republish the task applications to My webMethods Server 8.0.
For instructions, see webMethods Designer BPM Task Development Help 8.0.
3 My webMethods Server 7.x included a special component called a WebDAV folder
that was used if a folder in My webMethods Server needed to be exposed via
WebDAV. In My webMethods Server 8.0, the entire My webMethods Server
taxonomy is automatically exposed via WebDAV, so the WebDAV folder component
is no longer necessary and therefore has been removed. The upgrade procedure
automatically converted old webDAV folders into regular My webMethods Server
folders so no data is lost. However, the WebDAV URL of these folders has changed, so
clients must be updated. For more info about WebDAV support, see Administering My
webMethods Server 8.0.
4 In My webMethods Server 7.x, you could create home pages and add portlets to
them. The upgrade procedure converted your home pages to a new feature in 8.0
named workspaces, and converted your default 7.x home page to an 8.0 start page.
However, the upgrade procedure did not add the workspaces to your My
webMethods Navigation tab. For information about workspaces and instructions on
adding them to your Navigation tab, see Working with My webMethods 8.0.
c In the Archive File panel, select all projects that contain business processes. In the
To archive file field, specify the directory to which to export the projects. In the
Options area, you can accept the default file format options or select others. Click
Finish.
d Shut down Designer 7.x.
2 Import 7.x business process projects into Designer 8.0 as follows:
a Open Designer 8.0 and point to a new 8.0 workspace.
b Go to the File > Import wizard. In the Select panel, go to General > Existing Projects
into Workspace and then click Next.
c In the Import Projects panel, click Select Archive File, and then select the archive file
that contains the projects you exported. The projects appear in the Projects box;
select the projects to import and click Finish.
d Make sure the imported projects appear in the Solutions tab, under the Processes
node.
3 The Designer 8.0 local metadata implementation is different from that used in earlier
releases. Close all projects and then reopen them to re-extract local metadata from the
projects so users can search it.
4 If you are migrating from Designer 7.1.2, you must migrate your logical server
definitions as follows:
a Open Designer 7.1.2 and export the logical server definitions.
1 Go to Window > Preferences. On the Preferences dialog box, in the left navigation
bar, go to webMethods > Process Development > Logical Servers.
2 Click Export and identify the directory to which to export. You can export to
any directory; for example, you might export the logical server definitions to
the directory that contains the exported process models.
In the File name field, type the file name for the preferences. Designer will add
the file extension .properties. Click Open.
3 Click OK to close the Preferences dialog box.
b Open Designer 8.0 and import the logical server definitions.
1 Go to Window > Preferences. On the Preferences dialog box, in the left navigation
bar, go to Software AG > Integration Servers. The list on the left shows your logical
servers, called Integration Servers in Designer 8.0.
2 Click Import, select the .properties file you exported, and click Open. Designer
asks whether you want to overwriting existing servers; click OK twice.
3 Redefine the connections to the Integration Servers that will run process steps.
For instructions, see webMethods Designer Service Development Help 8.0.
Migrate Tasks
You migrate 7.x tasks by migrating different types of data, depending on your goals.
If you want to start new instances of migrated 7.x task application projects in 8.0, you
do not have any running 7.x task instances, and you do not need to resubmit any 7.x
task instances, migrate your design-time data to 8.0. Design-time data are your task
application projects.
If you want to finish 7.x task instances that are in progress or resubmit 7.x task
instances that have completed or failed, migrate your run-time data. Run-time data is
the complete set of information about 7.x task application projects and in progress or
completed 7.x task instances.
If you want to start new instances of migrated 7.x task application projects in 8.0, and
you want to finish 7.x task instances that are in progress or resubmit 7.x task instances
that have completed or failed, migrate both your design-time data and your run-time
data.
5 Click Start Migration. After the migration is complete, My webMethods Server displays
a message that lists the number of task instances it migrated.
6 Repeat these steps for all task instances to migrate.
Important! In the URLs, if you are using DB2, you must specify schema using all capital
letters. In addition, you must specify the options
CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000. These
settings will affect all database components in the same schema or database.
Select the check box next to each Load asset type for which you want to load
metadata. If you were monitoring Brokers or Integration Servers in your 7.x
environment, select those check boxes. If you will be monitoring Enterprise
Transaction Systems (ETS) assets, select the appropriate check boxes.
c Click Save.
5 Click each tab except the Validate tab that shows ; the icon changes to . If you
change any settings, and the tab has a Save button, click Save. When all tabs except the
Validate tab show , click the Validate tab.
Note: As a result of the KPI definition changes, data previously collected for IS
Service, Broker, and Custom Adapter common event maps are deleted during
migration.
4 Go to the Applications > Administration > Analytics > Infrastructure Components > Discovery
page. Click Add Asset. In the Asset Type list, click SNMP, and then follow the
instructions in Administering webMethods Optimize 8.0 to rediscover and monitor
SNMP agents.
Important! If a project build references a source server that is not connected, the
build will not be upgraded and you will have to rebuild it manually after
upgrade.
If a project references the Integration Server that hosts Deployer as a source
server, the project build will not be upgraded and you will have to rebuild it
manually after upgrade.
3 Start Deployer. Deployer automatically upgrades your project builds. For details and
errors, see the Integration Server 8.0 server log, stored by default in the Integration
Server_directory\logs directory.
4 Rebuild any project builds that were not upgraded because they referenced a source
server that was not connected in step 2, or because they referenced the Integration
Server that hosts Deployer as a source server.
Note: You do not have to add this option for Trading Networks because Trading
Networks caches its prepared statements using its own pooling mechanism.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38f
Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Back Up the 8.0 FCS webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Uninstall Certain Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Complete the EntireX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Complete the Web Services Stack Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Migrate Blaze Rules and Rule Maintenance Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Overview
This upgrade procedure explains how to install the latest webMethods 8.0 product
releases over webMethods 8.0 FCS products. In some cases, you will uninstall the FCS
products and then install the latest releases. In other cases, the installer will install the
latest releases in a new directory. In most cases, the Software AG Installer will install the
latest releases over the FCS products.
For some products, you must perform additional tasks to complete the upgrade or to
migrate data. This chapter provides instructions for those tasks.
Important! Because many products share files, you must upgrade all products that are
in the same installation directory.
You must upgrade products and migrate data in the order the instructions are
presented in this chapter.
Software AG strongly recommends that you upgrade and migrate in a controlled test
environment and test that environment for proper operation before upgrading and
migrating your production environments.
If you are going to upgrade My webMethods Server, the upgrade procedure will
reset the values below to their default values. If you customized any of these values,
start My webMethods Server, open My webMethods, and follow the steps below.
1 Shut down the 8.0 FCS products listed below if they are running on the machine on
which you are going to overinstall.
The instructions in the table are for Windows systems. On UNIX systems, use the
instructions provided in the product documentation.
2 Shut down all other applications that are running on the machine on which you are
going to overinstall.
Important! For My webMethods Server, you must back up the 8.0 FCS webMethods
installation directory and the MywebMethodsServer database component at the
same time. The two must be in sync, or you will experience problems. The same is
true for Optimize and the Optimize database components.
2 Back up all 8.0 FCS databases except Tamino XML Server. For instructions, see your
RDBMS vendor documentation.
3 Back up Tamino XML Server 8.0 FCS as follows:
a Start Tamino Manager. Under Tamino > Databases, click the node for a Tamino XML
Server database to back up.
b Under the database node, right-click the Backups node and then click Backup. The
Backup dialog box appears. Follow the instructions in the dialog box to create the
backup.
c Repeat these steps until you have backed up all of your Tamino XML Server
databases.
d Copy the backups to a safe location.
4 Back up CentraSite 8.0 SP1 as follows:
a Start the System Management Hub.
b Right-click the CentraSite > Registry/Repository > Backups node and then click Backup.
c Copy the backup to a safe location.
5 If you are going to upgrade My webMethods Server, go to the
8.0_installation_directory\MWS\server\server_instance\deploy directory and delete
all .xml files.
Uninstall CentraSite 8.0 SP1, Tamino XML Server 8.0, and Designer
8.0 (March 2009 Release)
Uninstall CentraSite 8.0 SP1, Tamino XML Server 8.0, and Designer 8.0 (March 2009
release). For instructions, see webMethods Installation Guide 8.0 and 8.0 SP1 (March 2009
release). The uninstallation of CentraSite 8.0 SP1 does not delete the Registry Repository
files or, on Windows systems, the Windows registry entries that point to those files.
When you install CentraSite 8.0 SP3, the installer will detect the Registry Repository 8.0
SP1 files and configure CentraSite 8.0 SP3 to use them.
Note: Trading Networks Additional Reports were merged into Trading Networks
Reports in the webMethods 8.0 GA release.
Important! If your products are distributed across multiple machines, install CentraSite
before installing any other product.
For installation directory, specify the 8.0 FCS webMethods installation directory.
If you have a cluster of Integration Servers, overinstall every Integration Server in the
cluster. If you have a cluster of My webMethods Servers, choose one node to
overinstall. You will upgrade the other nodes later, as described in “Migrate My
webMethods Server Data” on page 47.
On the Software AG Installer’s product selection tree, existing 8.0 FCS products are
shown in gray followed by the word “Installed” (wizard mode) or the letter “I”
(console mode). Select the latest 8.0 products to install; be sure to select all necessary
components of each product (see Software AG Installation Guide 8.0 GA, Typical
Development Installations for guidance).
If you are installing a product other than ApplinX and CentraSite that uses an
external RDBMS, select Database Configuration.
You can also select new products and optional items such as Documentation.
When the installer asks for product configuration information, do the following:
Product Action
Integration Indicate whether you want the installer to migrate Integration
Server Server 8.0 FCS data to the Integration Server 8.0 latest installation.
The installer will automatically run the Integration Server
Migration Utility to do the following:
Migrate the embedded database if you used it with Integration
Server 8.0 FCS.
Delete Integration Server 8.0 FCS configuration files, fixes, and
properties that are no longer used by Integration Server 8.0
latest.
Merge the Integration Server port.cnf and listeners.cnf files.
Note: You can instead choose to run the migration utility manually
after installation; see “Migrate Integration Server Data” on
page 45.
If you selected 8.0 products that are not yet installed on your machine, see
Software AG Installation Guide 8.0 GA for instructions on providing the required
product configuration information.
If you had the installer automatically migrate Integration Server data or upgrade My
webMethods Server server instances, details of the migration or upgrade are written
to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. If
you are using the installer wizard (as opposed to console mode), the installer’s Finish
panel provides a link to the file.
If you installed new 8.0 products, create any necessary database components. For
detailed information and instructions, see Software AG Installation Guide 8.0 GA.
System Actions
Windows Go to the Windows Services window and start the Software AG
EntireX Broker service.
UNIX Run this command:
EntireX_8.1_directory/bin/sag<x>etbsrv restart
Note: If you do not migrate the embedded database now, Integration Server 8.0
latest will migrate it automatically on startup.
c The utility asks whether to begin migration. If you want the utility to exit without
migrating any data, enter N. If you want the utility to migrate data based on the
settings you specified, enter Y; the utility prints progress messages to the
command window and the migration log. If migration completes successfully, the
utility does the following:
Deletes 8.0 FCS configuration files that are no longer used by Integration
Server 8.0 latest.
Deletes 8.0 FCS properties that are no longer used by Integration Server 8.0
latest from the 8.0 latest configuration files and merges the Integration Server
port.cnf and listeners.cnf files.
Deletes all fixes you applied to Integration Server 8.0 FCS.
Update WSDLs
In Integration Server Administrator, go to the Settings > Extended page. If you have the
extended setting watt.server.xml.ncname.encode.backward.compatibility and it is set to
true, reset it to false. Then regenerate the clients for all Provider Web services that have
an operation with field names starting with "xml" in the input signature, output
signature, header, or faults.
4 If you have a cluster of My webMethods Servers, delete the 8.0 FCS cluster nodes you
have not upgraded and then add 8.0 latest nodes. For instructions, see Administering
My webMethods Server 8.0.
Important! In the URLs, if you are using DB2, you must specify schema using all capital
letters. In addition, you must specify the options
CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000.
These settings will affect all database components in the same schema or database.
Re-enable Reports
If you upgraded Optimize or Monitor reports, reenable them. For instructions, see
Generating webMethods Reports 8.0 GA.
Important! If a project build references a source server that is not connected, the
build will not be upgraded and you will have to rebuild it manually after
upgrade.
If a project references the Integration Server that hosts Deployer as a source
server, the project build will not be upgraded and you will have to rebuild it
manually after upgrade.
3 Start Deployer. Deployer automatically upgrades your project builds. For details and
errors, see the Integration Server 8.0 server log, stored by default in the Integration
Server_directory\logs directory.
4 Rebuild any project builds that were not upgraded because they referenced a source
server that was not connected in step 2, or because they referenced the Integration
Server that hosts Deployer as a source server.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Back Up the 8.0 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Install 8.0 SPx Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Overview
This upgrade procedure explains how to install the latest 8.0 service packs over earlier 8.0
service packs.
Important! You must upgrade products and migrate data in the order the instructions
are presented in this chapter.
Software AG strongly recommends that you upgrade and migrate in a controlled test
environment and test that environment for proper operation before upgrading and
migrating your production environments.
1 Shut down the 8.0 products listed below if they are running on the machine on which
you are going to overinstall.
The instructions in the table are for Windows systems. On UNIX systems, use the
instructions provided in the product documentation.
2 Shut down all other applications that are running on the machine on which you are
going to overinstall.
Important! For Optimize, you must back up the 8.0 webMethods installation
directory and the Optimize database components at the same time. All must be in
sync, or you will experience problems.
2 Back up the 8.0 databases for the products you are upgrading. For instructions, see
your RDBMS vendor documentation.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Back Up 7.x Database Components and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Overview
This upgrade procedure explains how to upgrade webMethods 7.1.2, 7.1.3, 7.2, or 7.2.1
product releases to the latest webMethods 8.0 product releases.
Note: This procedure does not explain how to upgrade from CentraSite 7.x to Centra-
Site 8.0 SP3. If you need to perform that upgrade, contact Software AG Global Con-
sulting Services. CentraSite should be upgraded before any other product.
d In the Archive File panel, select all .process files or task application projects to
export. In the To archive file field, specify the directory to which to export. In the
Options area, you can accept the default file format options or select others.
e Click Finish.
f Shut down Designer.
2 If you want to shut down webMethods products, follow the instructions in the
webMethods 7.x product documentation.
Important! You do not have to shut down webMethods products; the installer
allows you to reassign webMethods product ports even if the products are
running.
Note: If you do not shut down all non-webMethods applications, the Software AG
Installer will not be able to replace key files that are locked by the operating
system.
4 If you are upgrading webMethods Broker, back up the JMS objects and data in each
webMethods Broker installation.
5 Back up the entire 7.x webMethods installation directory.
Important! For Optimize, you must back up the 7.x webMethods installation direc-
tory and the Optimize database components at the same time. All must be in sync,
or you will experience problems.
For the installation directory, specify a new webMethods directory except in the case
below.
If you are going to migrate business processes, you must continue using your
webMethods Broker 7.x storage, so you must install webMethods Broker 8.0 on the
machine that hosts webMethods Broker 7.x.
On the Software AG Installer’s product selection tree, select the 8.0 products to install;
be sure to select all necessary components of each product (see Software AG
Installation Guide 8.0, Typical Development Installations for guidance).
If you are installing a product that uses an RDBMS, select Database Configuration.
You can also select new 8.0 products and optional items such as Documentation.
Note: Do not choose to install CentraSite 8.0 SP3. If you need to upgrade from Cen-
traSite 7.x to CentraSite 8.0 SP3, contact Software AG Global Consulting Services.
When the installer asks for product configuration information, do the following:
Product Action
Trading Point the database connection at the 7.x Trading Networks
Networks database component.
Integration Regardless of your 7.x configuration, select the embedded
Server database. Later instructions will explain how to migrate your 7.x
data from your embedded database and external RDBMS.
webMethods If you do not want to continue using your 7.x storage, create a
Broker Broker Server configuration. The installer requires your 8.0
webMethods Broker license file to create a Broker Server
configuration.
If you want to continue using your 7.x storage, do not create a
Broker Server configuration.
Important! You must continue using your 7.x storage if you are
going to migrate business processes.
My Point the database connection at the RDBMS in which you will
webMethods create the new database component for My webMethods Server
Server 8.0 data.
Note: You will create the necessary database component after
installation.
If you selected 8.0 products that are not yet installed on your machine, see
Software AG Installation Guide 8.0 for instructions on providing the required product
configuration information.
Important! Do not create any other database components that you already have.
You will migrate the 7.x database components to 8.0 later in this procedure.
Important! On UNIX systems, you must enclose the database URL in double quotes.
Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service
configured for ;AlternateServers=(server:{1521|port};,…)
;ConnectionRetry=value; ConnectionDelay=value
RAC
;LoadBalancing=value[;option=value …]
For DB2, if the product will connect to a schema other than the
default schema for the specified database user, you must specify
these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT
PATH=current_path,schema"
Backward Compatibility
System Example
Windows server_config remove c:\webmethods7\Broker\data\awbrokers\default
When asked whether you want to remove the Broker Server from the Broker Server
Monitors server configuration, enter Y.
4 Create the 8.0 Broker Server and configure it to use the 7.x storage by going to the
webMethods Broker_8.0_directory/bin directory and running the command below. If
any part of the data directory path contains a space, enclose the entire path in quotes.
System Example
Windows server_config add c:\webmethods7\Broker\data\awbrokers\default
-k 8.0_license_file -p 6871
5 Make sure the 7.x storage is running under the 8.0 Broker Server:
System Steps
Windows You can do either of the following:
Open the Windows Services window. Make sure the status of the
webMethods Broker Server 8.0 (port) service is Started. Right-click the
service and click Properties. Make sure the value in the Path to
Executable field points to the awbroker file for 8.0.
Run this command:
C:\SoftwareAG\Broker\bin\server_config.exe list
You can run a custom migration, in which you choose which data to migrate. The
utility gathers your choices through a series of prompts, then migrates the specified
data. To run a custom migration, follow the steps below, in this section.
If you are performing migrations for multiple, identical, clustered Integration Servers
running on different machines, you can run a custom migration, export your choices
to file, and import the choices when you run the utility on other machines.
To run a custom migration and export your choices to file, follow the steps below, in
this section.
To run a migration with imported choices and a confirmation prompt before the
migration actually begins, follow the steps below, in this section. To run a migration
with imported choices silently (that is, with no confirmation prompt), see “Run the
Migration Utility Silently with Imported Settings, with a Zip File as Data Source, or
Both” on page 70.
You can create a Zip file of the Integration Server 7.x installation directory and use the
Zip file as the source of Integration Server 7.x data. One use of this option is when
your Integration Server 7.x and Integration Server 8.0 are on different machines. For
instructions, see “Run the Migration Utility Silently with Imported Settings, with a
Zip File as Data Source, or Both” on page 70.
During actual migrations, if migration of a piece of data fails (for example, certificate
settings for a port), the utility asks whether to continue with the next piece of data or
abort the migration. If you choose to abort, the utility exits. It does not revert the
Integration Server 8.0 installation. You can address the issue and run the utility again.
The migration utility writes details of the migration to the migrationLog.txt file in the
8.0_installation_directory\install\logs directory. By default, the utility writes INFO,
ERROR, and FATAL messages to the log. If you want to increase the logging level to
DEBUG, go to the Integration Server_8.0_directory\bin\migrate directory, open the file
log4j.properties file in a text editor, set the log4j.logger.Migration property to DEBUG,
MigrationFile, and save and close the file.
6 The utility asks whether to migrate port certificate settings to the keystores used in 8.0
SP1. You can migrate all of the settings (enter A), none of the settings (enter N), or
selected settings only (enter S). If you enter S, the utility lists each port and asks
whether to migrate its certificate settings.
For each SSL port you migrate, the utility will convert certificate settings into the
keystores used in 8.0 SP1. If conversion fails, the utility will revert all migration
changes it made to the port and disable the port in Integration Server 8.0 SP1.
Note: If you do not migrate certificate settings for a port, and a default Integration
Server keystore exists in the 8.0 SP1 installation, the port will default to that key-
store.
7 The utility asks whether to migrate remote server alias certificate settings. You can
migrate all of the settings (enter A), none of the settings (enter N), or selected settings
only (enter S). If you enter S, the utility lists each remote server alias and asks whether
to migrate its certificate settings.
For remote server alias you migrate, the utility will convert certificate settings to the
8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it
made to the remote server alias in Integration Server 8.0 SP1.
8 The utility asks whether to migrate Web service endpoint aliases. You can migrate all
of the aliases (enter A), none of the aliases (enter N), or selected aliases only (enter S).
If you enter S, the utility lists each Web service endpoint alias and asks whether to
migrate it.
For each alias you migrate that is in use by a WSD, the utility detects the type and
transport of the WSD and copies that information to the 8.0 SP1 files. If an alias is not
in use by a WSD, the utility copies the type and transport information in such a way
that the alias is available to all WSDs, regardless of type or transport.
The utility will convert type and transport information for Web service endpoint
aliases to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration
changes it made for the alias in Integration Server 8.0 SP1.
9 The utility asks whether to migrate Integration Server certificate settings. If you enter
Y, the utility will convert the certificate settings into the keystores used in 8.0 SP1.
10 The utility asks whether to migrate proxy settings. If you enter Y, the utility will
convert your proxy settings to the 8.0 SP1 format.
11 If Integration Server 7.x used the embedded database, the utility asks whether to
migrate it. If you enter Y, the utility will copy the database tables from Integration
Server 7.x to Integration Server 8.0 SP1 and convert the tables to the 8.0 SP1 format.
Note: If you do not migrate the embedded database now, Integration Server 8.0
SP1 will create the embedded database automatically on startup but not migrate
any data to it.
12 The utility asks whether to export the migration settings from this session. If you
enter Y, the utility stores the migration settings in a file named migrate.dat in the
directory from which you are running the utility.
13 The utility asks whether to begin migration. If you want the utility to exit without
migrating any data, enter N. If you want the utility to migrate data based on the
settings you specified, enter Y; the utility prints progress messages to the command
window and the migration log. If migration completes successfully, the utility does
the following:
Deletes 7.x configuration files that are no longer used by Integration Server 8.0
SP1.
Deletes 7.x properties that are no longer used by Integration Server 8.0 SP1 from
the 8.0 SP1 configuration files, and merges the Integration Server port.cnf and
listeners.cnf file.
If Integration Server 7.x was part of a cluster, upgrades your clustering
configuration to the 8.0 SP1 format.
Update WSDLs
Update your WSDLs. In Integration Server Administrator, go to the Settings > Extended
page. If you have the extended setting
watt.server.xml.ncname.encode.backward.compatibility and it is set to true, reset it to
false. Then regenerate the clients for all Provider Web services that have an operation
with field names starting with "xml" in the input signature, output signature, header, or
faults.
Run the Migration Utility Silently with Imported Settings, with a Zip
File as Data Source, or Both
If you want to run the migration utility silently using settings exported from an earlier
session, using a Zip file as the source of Integration Server 7.x data, or some combination
of these, follow the instructions below.
1 Go to the Integration Server_8.0_directory\bin\migrate directory on the machine on
which you ran the earlier migration session.
2 If you want to use exported settings, copy the migrate.dat file from that directory to
any directory on the machine on which you want to run the migration session.
3 If you want to use a Zip file as the source of Integration Server 7.x data, create a Zip
file of the entire contents of the Integration Server 7.x installation directory and then
copy the Zip file to the machine on which you want to run the migration session.
4 Open a command window, go to the Integration Server_8.0_directory\bin\migrate
directory, and run this command:
{migrate.bat|./migrate.sh}[options]
Option Enter
-destDir Full path to Integration Server 8.0 (for example,
C:\Software AG\IntegrationServer or /opt/webMethods7/Integra-
tionServer).
-silent true or false.
-importFile If you are using exported settings, full path to the migrate.dat file.
Option Enter
-srcDir If you are not using a Zip file as the 7.x data source, full path to Inte-
gration Server 7.x (for example, C:\webMethods7\Integration-
Server or /opt/webmethods7/IntegrationServer).
-srcFile If you are using a Zip file as the Integration Server 7.x data source,
full path to the Zip file.
Note: If you have a cluster of 7.x My webMethods Servers, the clustering configuration
was not migrated to your 8.0 installation. If you want to cluster 8.0 My webMethods
Servers, you will have to configure the cluster. For instructions, see Administering My
webMethods Server 8.0.
Apply Fixes
Apply the appropriate fixes below using the instructions in the fix readmes. Fixes are
available from the Software AG Knowledge Center.
longer have access permissions associated with them. If you export roles but you do not
export the users for those roles, the imported roles will have no users associated with
them.
Export Assets
1 Do one of the following:
Go to the My webMethods Server_7.x_directory\bin directory and enter the
command below. For target_ folder, specify the folder in which to create a folder
structure of all exported assets. Specify server_instance for server instances other
than the default. The root folder of the export folder structure will include a file
named info.properties that lists all exported assets.
Import Assets
1 Apply MWS_8.0_SP1_Fix2 and MWS_8.0_SP1_CL_Fix2 to My webMethods Server
8.0 using the instructions in the fix readme. Fixes are available from the Software AG
Knowledge Center.
2 Start My webMethods Server 8.0 by running this command:
3 Prevent new instances of 7.x process models from starting by shutting down all 7.x
Integration Servers that host Process Engines.
4 Migrate the ProcessEngine and ProcessAudit database components, as follows:
a Shut down all Integration Servers that connect to the 7.x ProcessEngine or
ProcessAudit database component.
b On the machine on which you installed the Database Component Configurator,
go to the webMethods_directory\common\db\bin directory, open a command
window, and migrate each database component by running the command below.
5 Start Integration Server 8.0 and connect the ProcessEngine and ProcessAudit
functions to the corresponding database components if they are not already
connected. For instructions, see Software AG Installation Guide 8.0.
6 Enable document retrieval for all triggers on Integration Server 8.0. For instructions,
see Administering webMethods Integration Server 8.0.
Migrate Tasks
Follow the instructions in “Migrate Tasks” on page 30.
Important! In the URLs, if you are using DB2, you must specify schema using all
capital letters. In addition, you must specify the options
CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000.
These settings will affect all database components in the same schema or
database.
3 Set up a new database pool for the new 8.0 MywebMethodsServer database
component as follows:
a Open My webMethods and go to the Applications > Administration > System-Wide >
Environments > Database Pool Configuration page. Click Add Pool. Complete the fields
and point at the 8.0 MywebMethodsServer database component.
b Go to the Applications > Administration > System-Wide > Environments > Define
Environments page. Under Environment Name, click the environment you imported.
Go to the Map DB Pools tab, map the common.directory - Analytic Engine Database
Component to the new database pool, and then click Save.
4 Go to the Applications > Administration > System-Wide > Environments > Define Environments
page. Under Environment Name, click the environment you imported.
5 If you are using Optimize for Infrastructure, follow the instructions in step 4 in “To
Reuse the 7.x CCS Environment Definition” on page 33.
6 Click each tab except the Validate tab that shows ; the icon changes to . If you
change any settings, and the tab has a Save button, click Save. When all tabs except the
Validate tab show , click the Validate tab.
Important! You must upgrade all source webMethods servers to the latest 8.0 release as
instructed in this chapter before you can migrate Deployer data.
4 Click Migrate Server Aliases. Deployer migrates the selected aliases, then disables those
rows and displays Yes in the Migrate column for the aliases.
4 In the Simulate Migration column, click in the row for each target group you want to
migrate. Deployer displays a message that indicates whether the aliases that are
referenced by the target group have been migrated. You must either migrate the
aliases or remove them from the target group in Deployer 7.x (see step 1).
5 In the Select column, select the check boxes next to target groups to migrate.
6 Click Migrate Target Groups. Deployer migrates the selected target groups, then disables
those rows and displays Yes in the Migrate column for the groups.
3 In the right-hand pane, in the Simulate Migration column, click in the row for each
project you want to migrate. Deployer displays a message that indicates whether the
source servers that are referenced by the project are running. If the message indicates
that any of the referenced source servers are not running, you must start the source
servers before you can migrate the project.
4 In the Select column, select the check boxes next to the projects to migrate.
5 Click Migrate Projects. Deployer displays a new window with a dynamic migration
report.
You can display the migration report for each project in the Report column in the
original window. You can display the latest migration report by clicking View Latest
Migration Report.
Note: You do not have to add this option for Trading Networks because Trading
Networks caches its prepared statements using its own pooling mechanism.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Back Up the 6.5 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Back Up 6.5 Databases and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Migrate webMethods Broker Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Migrate JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Migrate Access or Portal Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Overview
This upgrade procedure explains how to upgrade the latest webMethods 6.5 product
releases to the latest webMethods 8.0 product releases. For the products listed below, you
must perform additional tasks described in this chapter to complete the upgrade or to
migrate data.
webMethods Broker and JMS 6.5.2
Integration Server 6.5 SP3
Trading Networks 6.5 SP1
webMethods Access 6.5.2 or webMethods Portal 6.5.2
webMethods Modeler 6.5.1 SP1 and Process Run Time 6.5.1 SP1 (business processes)
Deployer 6.5 SP1
For simplicity, this chapter uses these terms:
The product releases from which you can upgrade are referred to as 6.5. However,
you can only upgrade from the releases listed above. If you want to upgrade from an
earlier release, you must first upgrade to the release listed above.
The latest webMethods 8.0 product releases to which you can upgrade are referred to
as 8.0.
Note: You cannot migrate Optimize or Manager Server from 6.5.1 SP2 to 8.0. Instead,
you must upgrade to 7.1.2 using instructions in webMethods Upgrade Guide 7.1, and
then upgrade from 7.1.2 to 8.0 using instructions in this guide.
You cannot migrate Workflow processes from 6.5 to 8.0. Instead, you must re-
implement your Workflow 6.5 projects using Designer 8.0 and Task Engine 8.0.
instructions, migrate the copied database components, and use the migrated database
components with your 8.0 products. This is not necessary for My webMethods Server
8.0, for which you will create a new database component.
1 If you want to shut down webMethods products, follow the instructions in the
webMethods 6.5 product documentation.
Important! You do not have to shut down webMethods products; the installer
allows you to reassign 6.5 webMethods product ports even if the products are
running.
Do not shut down the Integration Server Repository Server; it must continue
running until all data has been migrated.
2 Shut down all other non-webMethods applications that are running on the machine.
Important! If you do not shut down all non-webMethods applications, the Software
AG Installer will not be able to replace key files that are locked by the operating
system.
3 If you are upgrading webMethods Broker, back up the JMS objects and data in each
webMethods Broker installation.
4 Back up the entire 6.5 webMethods installation directory.
When the installer asks for product configuration information, do the following:
Product Action
Trading Point the database connection at the 6.5 Trading Networks
Networks database component.
Integration In the 6.5 release, internal configuration data was stored in the
Server Integration Server Repository. In 8.0, you can choose to store this
internal configuration data, called IS Internal data, in an
embedded database or an external RDBM. For complete
information, see the Data Storage chapter of Software AG
Installation Guide 8.0.
When you run the Integration Server migration utility after
installation, it will migrate your internal configuration data from
the Repository to the storage you choose here. It will also retain
your storage settings for IS Core Audit Log data.
webMethods If you do not want to continue using your 6.5 storage, create a
Broker Broker Server configuration. The installer requires your 8.0
webMethods Broker license file to create a Broker Server
configuration.
If you want to continue using your 6.5 storage, do not create a
Broker Server configuration.
Important! You must continue using your 6.5 storage if you are
going to migrate business processes.
Important! After Integration Server 8.0 and Developer 8.0 are installed, you will no
longer be able to launch Integration Server 6.5 and Developer 6.5 from the
Windows Start menu. You will have to launch these products from the command
line instead by running server.bat in the Integration Server_6.5_directory\bin
directory and developer.bat in the Developer_6.5_directory\bin directory.
If you selected 8.0 products that are not yet installed on your machine, see
Software AG Installation Guide 8.0 for instructions on providing the required product
configuration information.
After product installation is complete, create the 8.0 database components that the
table below indicates you should create. For instructions, see Software AG Installation
Guide 8.0.
If you installed new 8.0 products, also create any necessary database components for
those products. For detailed information and instructions, see Software AG Installation
Guide 8.0.
Important! Do not create any other database components that you already have.
You will migrate the 6.5 database components to 8.0 later in this procedure.
Important! On UNIX systems, you must enclose the database URL in double quotes.
Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service
configured for ;AlternateServers=(server:{1521|port};,…)
;ConnectionRetry=value; ConnectionDelay=value
RAC
;LoadBalancing=value[;option=value …]
For DB2, if the product will connect to a schema other than the
default schema for the specified database user, you must specify
these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT
PATH=current_path,schema"
Backward Compatibility
and territories, see “Migrate if You Do Not Have Gateways and Territories” on page 90. If
you have gateways and territories, see “Migrate if You Have Gateways and Territories”
on page 91.
If you chose to continue using your webMethods Broker 6.5 storage (for example,
because you want to migrate business processes), you did not create a 8.0 Broker Server
configuration during installation. You must now create a 8.0 Broker Server and configure
it to use the 6.5 storage. For instructions, see “Configure the 8.0 Broker Server to Use 6.5
Storage” on page 92.
d Select the check box next to the 8.0 Broker Server and click Import. If prompted,
click Skip SSL Configuration to not import the 6.5 Broker Server SSL configuration;
the 6.5 SSL configuration is incompatible with the 8.0 SSL configuration.
4 Your 6.5 Broker Server SSL configuration was not imported. If you are using SSL,
convert your SSL keystores to the correct format and configure SSL, including ACLs,
for the 8.0 Broker Server. For instructions, see Administering webMethods Broker 8.0.
c The Target Object area shows the webMethods Broker objects you can import. You
can change the target Brokers for your imported objects; to do so, click the Broker
links in the Target Object area and make the changes.
d Select the check box next to the 8.0 Broker Server and click Import. If prompted,
click Skip SSL Configuration to not import the 6.5 Broker Server SSL configuration;
the 6.5 SSL configuration is not compatible with the 8.0 SSL configuration.
e Repeat these steps for each territory whose configuration you exported.
5 If you exported and imported the local territory, you will have a one-sided gateway
from the remote territory to the local territory. To create a two-sided gateway, import
the local territory again.
6 Complete the gateway migration as explained below. For detailed instructions, see
Administering webMethods Broker 8.0.
If you installed webMethods Broker 8.0 on the same machine as webMethods
Broker 6.5 and the 8.0 Broker Server is using the 6.5 port, the gateways are
created, but you must manually set the document types to shared.
If you installed webMethods Broker 8.0 on a different machine than webMethods
Broker 6.5 or the 8.0 Broker Server is not using the 6.5 port, you must manually
create the gateways and set the document types to shared.
7 Your 6.5 Broker Server SSL configuration was not imported. If you are using SSL,
convert your SSL keystores to the correct format and configure SSL, including ACLs,
for the 8.0 Broker Server. For instructions, see Administering webMethods Broker 8.0.
4 Remove the 6.5 Broker Server from the 6.5 Broker Monitor startup configuration by
going to the webMethods Broker_6.5_directory\bin directory and running the command
below. If any part of the data directory path contains a space, enclose the entire path
in quotes.
System Example
Windows server_config remove c:\webmethods6\Broker\data\awbrokers\default
When asked whether you want to remove the Broker Server from the Broker Server
Monitors server configuration, enter Y.
5 Create the 8.0 Broker Server and configure it to use the 6.5 storage by going to the
webMethods Broker_8.0_directory/bin directory and running the command below. If
any part of the data directory path contains a space, enclose the entire path in quotes.
System Example
Windows server_config add c:\webmethods6\Broker\data\awbrokers\default
-k 8.0_license_file -p 6849
6 Make sure the 6.5 storage is running under the 8.0 Broker Server:
System Steps
Windows You can do either of the following:
Open the Windows Services window. Make sure the status of the
webMethods Broker Server 8.0 (port) service is Started. Right-click the
service and click Properties. Make sure the value in the Path to
Executable field points to the awbroker file for 8.0.
Run this command:
C:\SoftwareAG\Broker\bin\server_config.exe list
7 If you are using SSL, convert your keystores to the correct format. For instructions,
see Administering webMethods Broker 8.0.
Migrate C Clients
If you want to migrate C clients that use SSL to 8.0, you must modify the way SSL
connections are created in your C source code to reflect the Broker C API changes that are
documented below. These API changes are consistent with the 8.0 Broker Server SSL
configuration. For complete information on the 8.0 Broker Server SSL configuration, see
Administering webMethods Broker 8.0.
Changed Methods
These methods have been changed to accept the truststore file instead of the
distinguished name:
awGetDescriptorSSLCertificate
awSetDescriptorSSLCertificate
awGetSSLCertificate
For more information, see webMethods Broker Client C API Programmer’s Guide 8.0.
Removed Methods
These methods have been removed:
awGetSSLCertificateDns
awGetSSLRootDns
Backward Compatibility
6.5 JMS clients can run on 8.0 Broker Servers.
The SSL keystore format changed in release 7.x. If you have been using Spyrus keystore
files, you must migrate your keystores to the new format and bind the new location of the
keystore and truststore in your Connection Factories. For instructions, see Administering
webMethods Broker 8.0.
Library Locations
The table below lists changes to webMethods Broker and JMS JAR file names and
locations. You will have to make appropriate changes to the CLASSPATH for stand-alone
JMS clients and to settings for application servers used with JMS 8.0.
The utility deletes ports for the built-in Integration Server load balancer, which no
longer exists in Integration Server 8.0, and clustering ports, which are no longer
supported in Integration Server 8.0. You can reconfigure the Integration Server cluster
with a third-party load balancer later. The utility also upgrades ports whose format
has changed between the Integration Server 6.5 to 8.0 releases.
6 The utility asks whether to migrate port certificate settings to the keystores used in
8.0. You can migrate all of the settings (enter A), none of the settings (enter N), or
selected settings only (enter S). If you enter S, the utility lists each port and asks
whether to migrate its certificate settings.
For each SSL port you migrate, the utility will convert certificate settings into the
keystores used in 8.0. If conversion fails, the utility will revert all migration changes it
made to the port and disable the port in Integration Server 8.0.
Note: If you do not migrate certificate settings for a port, and a default Integration
Server keystore exists in the 8.0 installation, the port will default to that keystore.
7 The utility asks whether to migrate remote server alias certificate settings. You can
migrate all of the settings (enter A), none of the settings (enter N), or selected settings
only (enter S). If you enter S, the utility lists each remote server alias and asks whether
to migrate its certificate settings.
For remote server alias you migrate, the utility will convert certificate settings to the
8.0 format. If the conversion fails, the utility will revert all migration changes it made
to the remote server alias in Integration Server 8.0.
8 The utility asks whether to migrate Integration Server certificate settings. If you enter
Y, the utility will convert the certificate settings into the keystores used in 8.0.
9 The utility asks whether to migrate proxy settings. If you enter Y, the utility will
convert your proxy settings to the 8.0 format.
10 In separate prompts, the utility asks whether to migrate scheduled jobs, client
certificates, pub.storage settings, trigger join settings, and xref (cross-reference)
settings from the Repository to the storage (embedded database or external RDBMS)
you specified in the installer.
11 The utility asks whether to export the migration settings from this session. If you
enter Y, the utility stores the migration settings in a file named migrate.dat in the
directory from which you are running the utility.
12 The utility asks whether to begin migration. If you want the utility to exit without
migrating any data, enter N. If you want the utility to migrate data based on the
settings you specified, enter Y; the utility prints progress messages to the command
window and the migration log. If migration completes successfully, the utility does
the following:
Deletes 6.5 configuration files that are no longer used by Integration Server 8.0.
Deletes 6.5 properties that are no longer used by Integration Server 8.0 from the
8.0 configuration files, and merges the Integration Server port.cnf and
listeners.cnf file.
The Integration Server 6.5 Repository Server was replaced in Integration Server
8.0 by a set of database tables collectively called IS Internal. If you chose the
embedded database during installation, the utility migrates your Repository
Server data to the embedded database, which contains IS Internal database tables.
If you pointed to an external RDBMS during installation and then created the IS
Internal database component, the utility migrates your Repository Server data to
the IS Internal database component in the external RDBMS.
The 6.5 files are in the backup you took before installing 8.0. The 8.0 files are located in
the Integration Server_8.0_directory\bin directory.
Note: The built-in Integration Server load balancer no longer exists in release 8.0. If
you were using the built-in load balancer, and want to continue using load
balancing, switch to a third-party load balancer.
MigratePropFile.{bat|sh} path_to_6.5_properties_file
For example:
MigratePropFile.sh
/opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf
migratedata_to_tn_7-1.{bat|sh} 6.5
3 Review the command window to make sure the migration was successful. If errors
occurred, contact Software AG Customer Care.
Note: Because processing rule names must be unique, the migration utility scans
the data for duplicate rule names. If it finds duplicates, the utility adds a sequence
number to the each rule name to make the names unique.
Table Fields
BizDocAttributeDef LastModified
BizDocTypeDef LastModified
BizDoc DocTimestamp, LastModified
BizDocAttribute DateValue
BizDocArrayAttribute DateValue
DeliveryJob TimeCreated, TimeUpdated
ProcessingRule LastModified
ActivityLog Entry Timestamp
Table Fields
TPA TimeCreated, LastModified
EDITracking DocTimestamp, FATimestamp
EDIStatus LockTimeStamp, TimeCreated
setcp.{bat|sh}
Parameter Value
Integration Server_8.0_ Full path to the Integration Server 8.0 directory.
directory
date1 dd-Mmm-YY To convert the date and time stamps for all Trading
Networks data that was created on or before a specified
date2 dd-Mmm-YY
date, specify that date as date1 dd-Mmm-YY.
To convert only data that was created on or between two
dates, specify those dates as date1 dd-Mmm-YY and date2
dd-Mmm-YY.
For example, to convert all data created on or between July 1 and December 31 2008
for a Trading Networks whose time zone is 10 1/2 hours ahead of GMT, and to
commit the converted date and time stamps to the Trading Networks database
component, you would enter:
Note: If you have a cluster of 7.x My webMethods Servers, the clustering configuration
was not migrated to your 8.0 installation. If you want to cluster 8.0 My webMethods
Servers, you will have to configure the cluster. For instructions, see Administering My
webMethods Server 8.0.
Apply Fix
Apply MWS_6.5.2_Fix3 to Access or Portal 6.5 using the instructions in the fix readme.
Fixes are available from the Software AG Knowledge Center.
Export Assets
1 Do one of the following:
Go to the Access_or_Portal_6.5_directory\bin directory and enter the command
below. For target_ folder, specify the folder in which to create a folder structure of
all exported assets. Specify server_instance for server instances other than the
default. The root folder of the export folder structure will include a file named
info.properties that lists all exported assets.
Log on to Access or Portal as PortalAdmin and go to the Portal Content > Content
Migration Wizard page. Under Migration Properties, select Package for Migration Source
Type and Export for Migration Mode, and then click Next. Under Export Properties for
Side By Side Upgrade, specify the full path to target_ folder. In the Export Descriptor
field, specify the full path to the asset descriptor file. Click Next to begin the
export. The export process might take several minutes.
2 Check the log file exportyyyy-mm-dd-yyyy hh mm ss.log in the
Access_or_Portal_6._directory\server\server_instance\logs directory. If errors
occurred, contact Software AG Customer Care.
3 Move the contents of the target folder to the machine that hosts My webMethods
Server 8.0.
Import Assets
Follow the instructions in “Import Assets” on page 74.
If you want to start new instances of migrated 6.5 process models in webMethods 8.0,
and you want to finish 6.5 process instances that are in progress or resubmit 6.5
process instances that have completed or failed, you must migrate both your design-
time and run-time data.
a Shut down all Integration Servers that connect to the 6.5 ProcessTrackingStore
and ProcessAudit database components.
b Do the following for your RDBMS:
RDBMS Action
Oracle Execute the ora_pra_m_10_to_20_metadata.sql script in the
8.0_installation_directory\common\db\
scripts\oracle\processaudit\migrate\10_to_20 directory from
your database editor.
SQL Server Execute the mss_pra_m_9_to_10_indexnames.sql script in the
8.0_installation_directory\common\db\
scripts\mssql\processaudit\migrate\10_to_20 directory from
your database editor.
DB2 for From your database editor, do the following:
Linux,
1 Execute the db2_pra_m_9_to_10_migrate.sql script and then
UNIX,
the db2_pra_m_dml_tracking.sql script. The scripts are in
Windows
the 8.0_installation_directory/common/db
/scripts/db2/processaudit/ migrate/9to10 directory.
2 Execute the db2_pre_m_9_to_10_migrate.sql script and then
the db2_pre_m_dml_tracking.sql script. The scripts are in
the 8.0_installation_directory/common/db/scripts/
db2/processengine/migrate/9to10 directory.
3 Start Integration Server 8.0 and connect the ProcessEngine and ProcessAudit
functions to the corresponding database components if they are not already
connected. For instructions, see Software AG Installation Guide 8.0.
4 Enable document retrieval for all triggers on Integration Server 8.0. For instructions,
see Administering webMethods Integration Server 8.0.
Note: You do not have to add this option for Trading Networks because Trading
Networks caches its prepared statements using its own pooling mechanism.