Getting Started

webMethods Cloud Container offers the ability to use Software AG Designer, the full-featured professional development environment, to deploy packages and configurations that reside within on-premises runtimes or repositories to Cloud Container.

Choose from predefined cloud solution landscapes, let Software AG handle landscape provisioning, deploy the packages and configurations, manage fixes, patches and upgrades, and provide CI/CD support in the cloud. Then explore out-of-the-box monitoring dashboards to track solution health as well as alerts.

Let's get started

Using Software AG Designer or by employing the Continuous Integration (CI) approach, you can seamlessly deploy your on-premises webMethods Integration Server packages, Adapter packages, webMethods CloudStreams packages, configuration assets, and customized configurations to solutions created on webMethods Cloud Container. In the webMethods Cloud Container context, configuration assets are limited to webMethods Integration Server and Universal Messaging configurations. To know more about how Software AG manages cloud deployment and operations, click here.

See the following video to quickly get started with webMethods Cloud Container.

Installation requirements

Click here for information on installation requirements.

webMethods Cloud Container supports several commonly used web browsers such as Mozilla Firefox, Google Chrome, and Microsoft Edge.

Create a Solution

You must first create a solution in webMethods Cloud Container before deploying the on-premises assets and configurations. After you launch webMethods Cloud Container, click Solutions > Solution List. The Solution List page displays the solutions created in webMethods Cloud Container.

Note: You must have the required permissions under Settings > Access Profiles > Administrative Permissions > Functional Controls > Solution to create, or delete Solutions.

Note: Further, you cannot modify the solution name after it is created.

When you create a solution from the predefined landscape templates, you can set the number of CPU core to 1, 2, and 4 and Memory to 2, 4, 6, 8, and 16 in GB. Note that the allocated configurations (CPU and Memory) of Integration Server node is shared by processes other than Integration Server runtime as well. For example, if a user is configuring 4 GB memory when creating a solution using the landscape template with Integration Server connected to Universal Messaging, then an approximate of 3.6 GB configurations is used for Integration Server and the rest would be shared by other processes.

To create a solution:

  1. Log in to webMethods Cloud Container.

  2. Click Solutions > Solution List. The Solution List page appears.

  3. From the Solution List page, click Create New Solution to create a solution.
    Note: Solutions created using a trial account are deactivated daily by UTC +01:00 AM. After you log in, you need to reactivate the solutions. All assets will be available after a short delay.

  4. Select the landscape model that best represents your environment. The supported landscapes are: (a) webMethods Integration Server with a BigMemory Max server
    (b) webMethods Integration Server with Universal Messaging and a BigMemory Max server
    (c) webMethods Integration Servers with Universal Messaging, and a BigMemory Max stripe
    (d) Universal Messaging

  5. Click OK.
    In the New Solution page, fill in the solution Name, the solution Description, the name of the webMethods Integration Server and Universal Messaging instances, number of CPU Cores, and Memory characteristics of the hardware to support each service in the solution landscape. You can also select the webMethods Integration Server and Universal Messaging icons to highlight the sections in the New Solution page. BigMemory Max is available only when webMethods Integration Server runs in a stateful clustered mode.

    For more information about creating a solution, see Creating Solutions.

Deploy on-premises packages and configurations

Using Designer you can deploy your on-premises Integration Server packages and configuration assets to webMethods Cloud Container. Before deploying the packages and configuration assets, you must configure a connection to webMethods Cloud Container. Click here for more information.

After you publish the assets and configurations to webMethods Cloud Container, you can move the assets from one environment to another environment. Click here to know more about environments.

Execute Services

After you deploy the on-premises assets, you can view and run the services by using the Service Editor. Click here to know more about services.

DBaaS availability

The following table shows the regions where DBaaS capability is currently available.

Regions DBaaS Support
EU1 Ireland AWS Yes
US1 Oregon AWS No
EU2 Frankfurt AWS No
AU2 Sydney AWS No
EU3 West Azure No
US2 East Azure No
AU1 Australia East Azure No

More Help

It is now easier to find other technical information about Cloud Container in the vast pool of assets on TECHcommunity. Click the below links to know more.

Topics Links
Monitoring UM on Cloud Container
Cloud Deployment using ABE
Not just Lift and Shift - Freedom to Lift-Think-Shift, Lift and Re-shape
What is your Cloud Transformation Strategy?
Integration and Cloud Computing
Connecting to UM from External Clients
Deploying Custom Libraries and Certificates
webMethods Cloud Container-Cloud Storage
API Invocation using Invoke, REST, SOAP and OData
Manual Deployment
Deploying Resource Configurations
Deploying SFTP Configurations
Deploying IS Packages to Integration Server Including Runtime Configuration
Deploying IS Packages to Integration Server with Variable Substitution
Executing Services using Two-way SSL API Invoke
Deploying File Access Controls
Deploying Schedulers
Direct Deployment from Designer using Include runtime configuration
Deploying Messaging Configurations
Cloudstreams Support
Unit Test Framework(UTF)
Variable Substitution, Deployment, Rollback and Deletion
Deploying UM Assets