•  Upgrading Software AG Products On Premises
  •  General Information
    • Document Conventions
    • Online Information and Support
    • Data Protection
  •  Prepare for Upgrade
    • Upgrades Covered in This Guide
    • Preparing, Planning, and Testing
    • Using Software AG Installer, Software AG Update Manager, Database Component Configurator, and Migration Utilities to Upgrade
    • Using Command Central to Upgrade
    • Documentation Needed to Perform the Upgrade
    • Troubleshooting
    • Support for Upgrade Across Operating Systems
    • General Upgrade Procedure Requirements
    • Upgrades and Migrations Covered in Other Guides
  •  Upgrade Software AG Infrastructure
    • Install the New Product
    • Prepare the Old Installation
    •  Migrate Software AG Infrastructure
      • Configurations, Data, and Assets that Will be Migrated
      • Run the Software AG Infrastructure Migration Utility
    • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Metering
    • Install the New Products
    •  Upgrade Metering Agent
      • Prepare the Old Installation
      •  Migrate Metering Agent
        • Configurations that will be migrated
        • Cached measurements that will be migrated
        • Run the Metering Agent Migration Utility
    •  Upgrade Metering Server
      • Prepare the Old Installation
      •  Migrate the Metering Server
        • Folders and Locations that Will be Migrated
        • Run the Metering Server Migration Utility
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade BigMemory Max or Terracotta
    • Install the New Product
    • Prepare the Old Installation
    • Migrate BigMemory Max
    •  Migrate Terracotta
      • Migrate Terracotta Management Console Configuration and Data
      • Migrate Ehcache 3.x Data
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Universal Messaging
    •  Universal Messaging Upgrade Guidelines
      • Universal Messaging Cluster Upgrade Guidelines
    • Install the New Product
    • Prepare the Old Installation
    •  Migrate Universal Messaging
      • Configurations, Data, and Assets that Will be Migrated
      •  Run the Migration Utility
        • Perform a Custom Migration
        •  Migrate Using Imported Settings
          • Migrate Using Custom Imported Settings with Prompting
          • Migrate Using Custom Imported Settings without Prompting (Silent)
          • Migrate Using Default Imported Settings without Prompting (Silent)
    • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade My webMethods Server
    • Cluster Upgrade Guidelines
    • Install the New Product
    • Prepare the Old Installation
    • Migrate Database Components
    •  Migrate My webMethods Server
      • Instances, Configurations, Data, and Assets that Can be Migrated
      •  Run the Migration Utility
        • Perform a Custom Migration
        •  Migrate Using Imported Settings
          • Migrate Using Custom Imported Settings with Prompting
          • Migrate Using Default Imported Settings without Prompting (Silent)
          • Migrate Using Custom Imported Settings without Prompting (Silent)
    •  Complete the My webMethods Server Upgrade
      • Check Java Service Wrapper #include Directives
      • Initialize a My webMethods Server Instance
      • Switch from Clone Migrated Database to Live Migrated Database
    • Complete the Business Rules Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Integration Server or Microservices Runtime and Hosted Wm Packages
    • Cluster Upgrade Guidelines
    • Install the New Products
    • Prepare the Old Installation
    • Migrate Database Components
    •  Migrate Integration Server or Microservices Runtime and Hosted Wm Packages
      • Configurations, Data, and Assets that Can or Will be Migrated
      •  Run the Migration Utility
        • Perform a Custom Migration
        •  Migrate Using Imported Settings
          • Migrate Using Custom or Default Imported Settings with Prompting
          • Migrate Using Custom or Default Imported Settings without Prompting (Silent)
    •  Complete the Integration Server Upgrade
      • Check Java Service Wrapper #include Directives
    •  Complete the Integration Server or Microservices Runtime Upgrade
      • Customize Startup Files
      • Update WSDLs
      • Upgrade from 10.1: Save and Synchronize an Updated Publishable Document Type
      • Connect Integration Server or Microservices Runtime and Hosted Products to Database Components
    • Complete the Adapters or eStandards Modules Upgrade
    • Complete the ActiveTransfer Upgrade
    •  Complete the CloudStreams Upgrade
      • Configure TLS 1.1 and 1.2 Trust Store
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Software AG Designer and Business Process Data
    • Install the New Software AG Designer
    • Prepare the Old Software AG Designer
    • Migrate Database Components
    •  Migrate Software AG Designer
      • Before Migrating
      • Migrate Apama, Application Platform (Deprecated), Business Process, and Business Rule Projects
      • Migrate Task Application Projects
      • Redo Attachment List Control Customizations in CAF Applications
      • Migrate CloudStreams Server Definitions and Projects
      • Migrate Integration Server or Microservices Runtime Definitions
      • Migrate Mobile Projects
    • Complete the Business Process Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Infrastructure Data Collector
    • Install the New Product
    • Prepare the Old Installation
    •  Migrate Infrastructure Data Collector
      • Configurations, Data, and Assets that Can be Migrated
      •  Run the Migration Utility
        • Perform a Custom Migration
        •  Migrate Using Imported Settings
          • Migrate Using Custom or Default Imported Settings with Prompting
          • Migrate Using Custom or Default Imported Settings without Prompting
      • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Optimize
    • Install the New Product
    • Ways to Migrate
    • Prepare the Old Installation
    • Migrate Database Components
    • Configure and Start the Terracotta Server Array
    • Update Connections to Other Products
    •  Migrate Optimize
      • Configurations, Data, and Assets that Can be Migrated
      • Upgrade from 9.12 or Later: Migrate Using the Migration Utility
      •  Upgrade from 9.9 or Later: Migrate Using the Define Environments Page in My webMethods Server
        • Not Reuse the Old Central Configurator System (CCS) Environment Definition
        • Reuse the Old CCS Environment Definition
        • Deploy the New Optimize Environment
      • Switch from webMethods Broker to Universal Messaging
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade the Asset Build Environment, Deployer, or Application Platform (Deprecated)
    • Install the New Product
    • Upgrade the Asset Build Environment
    •  Upgrade Deployer
      • Prepare the Old Installation
      •  Migrate Deployer
        • Configurations, Data, and Assets that Will be Migrated
        • Run the Migration Utility
    •  Upgrade Application Platform (Deprecated)
      • Prepare the Old Installation
      •  Migrate Application Platform
        • Configurations, Data, and Assets that Will be Migrated
        • Run the Migration Utility
      •  Complete the Upgrade
        • Verify and Correct Package Imports
        • Update the Tomcat Configuration
        • Upgrade from 9.9, 9.10, or 9.12: Complete the WmTomcat Web Applications Migration
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Apama
    • Install the New Product
    • Prepare the Old Installation
    • Migrate Apama
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Developer Portal, API Gateway, API Portal, or CentraSite
    • API Gateway Cluster Upgrade Guidelines
    • Install the New Products
    •  Upgrade API Gateway
      • Prepare the Old Installation
      • Migrate Database Components
      •  Migrate API Gateway
        • Configurations, Data, and Assets that Will be Migrated
        • Perform the Migration
    •  Upgrade Developer Portal
      • Prepare the Old Installation
      • Assets that are Migrated
      • Perform the Migration
    •  Upgrade API Portal
      • Upgrade from 9.9 through 10.5: Prepare the Old Installation
      •  Migrate API Portal
        • Assets that Can be Migrated
        • Perform the Migration
      • Complete the Upgrade
    •  Migrate API Portal 10.7 to Developer Portal 10.15
      • Prepare the Old Installation
      •  Migrate API Portal to Developer Portal
        • Assets that Can be Migrated
        • Limitations
        • Perform the Migration
        • Complete the Migration
    •  Upgrade CentraSite
      • Prepare the Old Installation
      •  Migrate CentraSite
        • Configurations that Will be Migrated
        • Run the Migration Command
      • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade MashZone NextGen
    • Install the New Product
    •  Upgrade from 10.1 or 10.3: Migrate MashZone NextGen
      • Prepare the Old Installation
      •  Migrate MashZone NextGen
        • Configurations, Data, and Assets that Will be Migrated
        • Run the Migration Utility
      • Complete the Upgrade
    •  Upgrade from 9.10 or 9.12: Migrate MashZone NextGen
      • Prepare the Old Installation
      •  Set Up the MashZone NextGen Repository
        • Set Up the Repository When Using the Embedded Derby Database
        • Set Up the Repository When Using Any Other Database
      • Upgrade from 9.10: Add Data from the Old Repository to the New Repository
      •  Update the MashZone NextGen Configuration and Copy Extensions
        • Update When an External Configuration Directory Was Used
        • Update When No External Configuration Directory Was Used
      • Upgrade from 9.10: Migrate Feeds and Run Upgrade Commands
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade from 9.9: Upgrade Mobile Designer
    • Install the New Product
    • Prepare the Old Installation
    • Migrate Mobile Designer
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade webMethods OneData
    • Gather Information for Installation
    • Install the New Product
    • Prepare the Old Installation
    • Migrate Database Components
    •  Migrate webMethods OneData
      • Configurations, Data, and Assets that Will be Migrated
      • Run the Migration Utility
    • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Zementis Predictive Analytics
    • Install the New Product
    • Prepare the Old Installation
    •  Migrate Zementis Predictive Analytics
      • Assets that Will be Migrated
      • Run the Migration Command
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Upgrade Digital Event Services (Deprecated)
    • Digital Event Services Deprecation
    • Install the New Product
    • Prepare the Old Installation
    •  Migrate Digital Event Services (Deprecated)
      • Configurations, Data, and Assets that Will be Migrated
      • Run the Migration Utility
      • Complete the Upgrade
    • Configure Products, Update Host Names, Adjust Assets for Release Changes, Re-enable Auto-Startup
  •  Migrate Database Components
    • Requirements and Cautions
    • Prepare Database Components for Migration
    • Migrate Database Components Using Database Component Configurator
  •  Upgrade Using Command Central
    •  Supported Upgrade Scenarios
      • Same Installation Directory, Hosts, and Ports; Live Database
      • New Installation Directory, Same Hosts and Ports, Cloned Database
      • New Installation Directory and Ports, Same Hosts, Cloned Database
      • New Hosts, Live or Cloned Database
    • Upgrade Approaches
    • Upgrade Products in a Single Environment
    • Upgrade Products Using Software Stacks (10.1 and Later)
• Copyright

Upgrading Software AG Products On Premises

Copyright