Table of Contents Previous Next



Use the Add Engine dialog (see Figure 4.16) to define an engine. To access the Add Engine dialog, connect to the Ark console as a user with administrative privileges, navigate to the Admin tab, and select Add Engine.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\d57262a7\Screen Shot 2018-12-07 at 11.27.19 AM.png
Use the fields on the Add Engine dialog to define a new server image/database pairing; please note that some fields are disabled if the server is statically provisioned:
Use the ID field to provide an identifier for the engine. Please note that the identifier must be unique, and may not be modified after saving the engine.
Use the drop-down listbox in the DB Type field to select the type of database used in the pairing.
Use the drop-down listbox in the Version field to specify the server version.
Use the Name field to provide a name for the pairing. When the engine is enabled, the specified name will be included for use on the Create Cluster dialog.
Use the drop-down listbox in the Server Type field to specify the server image on which the database will reside. The drop-down listbox displays those images previously defined on the Add Server dialog.
Use the drop-down listbox in the RHEL Subscription field to select the Red Hat Subscription Manager service that will be used by the engine. To populate the RHEL Subscription drop-down, describe your subscription services in the RHEL Subscription Management section of the Admin tab. RHEL Subscription Manager services are only applicable for RHEL 7 clusters.
Use the Yum repo URL field to provide the URL of the yum repository that will be used to initially provision database packages and to later update the database packages during cluster upgrade operations.
http://[user_name[:password]@]repository_url
user_name specifies the name of a user with sufficient privileges to access the repository.
password specifies the password associated with the repository user. Please note that if your password contains special characters (such as a $), you may need to percent-encode the characters.
repository_url specifies the URL of the repository.
Please contact your EnterpriseDB account manager for connection credentials (the values specified in the user_name and password placeholders) for the EnterpriseDB repositories.
When specifying multiple repositories in the Yum repo URL field, specify one repository per line. When you perform an update, any available updates in all of the specified repositories will be applied.
Use the Required DB Packages field to provide a space-delimited list of packages that have been tested by EDB as the required minimum set to build a functional cluster instance.
Use the Optional Node Packages field to provide the names of any packages that should be installed (from the specified repository) on every cluster node during provisioning.
Please note: packages added via the Optional Node Packages field on the master node of the cluster will also be provisioned on any standby nodes that are subsequently created. If the package requires manual configuration steps, you will be required to repeat those steps on each node of the cluster; package configurations will not be propagated to standby nodes. If you add a node through cluster operations (such as failover, scaling, or restoring a node from backup), any packages on the new node will require manual configuration.
When you have completed the dialog, click Save to create the engine definition, or Cancel to exit without saving.
To modify an engine, use the Edit Engine Details button to open the Edit Engine Details dialog (see Figure 4.17).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\c5e153b2\Screen Shot 2018-12-07 at 11.31.47 AM.png
Use fields on the Edit Engine dialog to specify property changes to an engine. When you’re finished, click the Save button to make the changes persistent and exit, or Cancel to exit without saving.
You can use the disabled box to specify that an engine is (or is not) available for use in new clusters without removing the engine definition:
Click the Save button to make any changes to the Edit Engine Details dialog persistent, or select Cancel to exit without modifying the engine definition.
To delete an engine, highlight an engine name in the DB Engine Administration list, and select the Delete Engine button. A dialog will open, asking you to confirm that you wish to delete the selected engine (see Figure 4.18).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\08934c2b\Screen Shot 2018-10-16 at 10.48.02 AM.png
Click the Delete button to remove the engine definition, or select Cancel to exit without removing the engine definition.


Table of Contents Previous Next