For optimal performance, you can add a MySQL database to your Cloud Container subscription. This enables you to configure, store, and monitor your database directly in the cloud instead of using external systems. The database endpoint can be shared by multiple solutions deployed by the tenant.
To create a database instance in the cloud
On the home page in webMethods Cloud Container, under Database, click Learn more, and then click Start database setup.
On the Database setup details screen, do the following:
a. In the Database instance identifier field, specify a name for the database.
Important: Each Software AG Cloud tenant can create only one database instance.
b. In the Create DB master username and DB master password fields, specify the username and password that you will use to access the database.
Note: The master user has full privileges on the database. For more information on database privileges, see the MySQL documentation.
c. Select Encrypt databaseif you want to enable the encryption of database data and click Continue. Note that you cannot change the encryption settings after the database is created.
When the database configuration is complete, you are redirected to the home page of webMethods Cloud Container where the Database element shows that the database server is running.
After you create the database instance in the cloud, you can connect one or more solutions to it.
To connect a solution to the database instance in the cloud:
Enable the wMJDBCAdapter package for the solution. For more information, see the Solutions chapter in webMethods Cloud Container.
In Software AG Designer, deploy to the cloud the on-premises webMethods Integration Server packages that you want to include in the solution.
a. In the Package Navigator view, right-click any of the packages that you want to include and select Deploy to Cloud.
b. In the Publish Assets to webMethods Cloud dialog box, select all packages that you want to include in the solution and click Next.
c. In the Integration Server Packages Variable Substitution dialog box, do the following for each of the packages that have JDBC connections:
Enable the State after Deployment property.
In the user, password, and serverName fields, specify the username, password, and host name of the database instance in the cloud.
Note: You can see the host name of the database in the DB instance endpoint field on the Database page in webMethods Cloud Container.
d. In the Select the webMethods Cloud Solution dialog box, select the solution that you want to connect to the database and click Finish.
To secure the connection between a solution and the database
Import the Amazon RDS Root CA certificate as a trusted certificate in a Java keystore. For more details on the certificate, see the Amazon Relational Database Service documentation.
Copy the truststore to the config directory of any of the packages you deploy to the solution.
In the web administration interface of the on-premise webMethods Integration Server, go to Adapters > WebMethods Adapter for JDBC > Connections. In the Other Properties field of the JDBC adapter connection, specify:
sslMode=VERIFY_IDENTITY;
trustCertificateKeyStoreUrl=file:packages/<package>/config/<truststore>;
trustCertificateKeyStorePassword=<password>
where package is the name of the package that contains the truststore, truststore is the name of the keystore that contains the trusted certificate, and password is the password to the truststore.
In Software AG Designer, deploy the updated packages to the cloud.
Note: Amazon Relational Database Service currently does not support authentication that uses a client certificate.
After you create the database instance in the cloud, you can monitor its status on the Database page in webMethods Cloud Container.
On the Database dashboard of the Database page, you can view the following elements:
| Element | Description |
|---|---|
| DB CPU usage | CPU usage in percentage. |
| DB storage size | The allocated storage space and the storage space used by the database. |
| DB server status | Shows if the database server is running. You can start or stop the server at any time by clicking Start server or Stop server. |
In the Configuration details section of the Database page, you can view the following fields:
| Field | Description |
|---|---|
| DB instance | The size of the database, based on your license offering. |
| DB instance identifier | The name of the database. |
| DB instance endpoint | The host and port that you can use to access the database. |
| Allowed IPs | The list of external IPs that can access the database. It is recommended to use the database only from applications in Software AG Cloud. By default, you can access the database only in the cloud. For administrative purposes you can enable access to the database from external IPs. To add external IPs, click Edit and type each IP on a new row. The supported IP format is Classless Inter-Domain Routing (CIDR) block format, xxx.xxx.xxx.xxx/yy. If you specify only xxx.xxx.xxx.xxx, mask /32 is automatically added. |