Managing Nodes

Adding Nodes

To add a node to a running environment:

1. Click the Related Actions button corresponding to the environment.

2. Select Manage Node.

3. Expand the Select Actions section if necessary, and select Add action.

4. Select Type.

5. Select the Operating System.

6. If the type is Middle Tier then there is an option to select an existing MT node from which configuration/custom configuration can be copied for the node being added.

7. Enter the required credentials and settings.

8. Click Submit and confirm.

9. Scale Up process status are:

   • InitiatingScaleup

   • ScaleUpInProgress

   • Running

   • ScaleupFailed

Navigation:

Click the Related Actions button corresponding to the environment. Select Manage Node. The Manage Node page is displayed.

This example illustrates the fields and controls on the Manage Node page for adding a Windows middle tier node.

The APP_HOME (Application home, or app home) and CUST_HOME (custom home, or cust home) paths are not mandatory when adding a Windows middle tier. However if you want to copy contents from the app home and/or cust home to the Windows middle tier perform the following:

1. Create a directory inside file server mount in the Cloud Manager. For example:

   1. Create a directory ps_app_home_win inside /cm_psft_dpks.

   2. Place the app_home contents as a zip file inside this directory.

   3. Create a directory ps_cust_home_win inside /cm_psft_dpks.

   4. Place the cust_home contents as a zip file inside this directory

2. Provide the path to app home (APP_HOME) and/or cust home (CUST_HOME). For example: ps_app_home_win and ps_cust_home_win.

3. When the Windows middle tier node is provisioned, the contents in the zip file will be extracted to the VM instance.

See Adding Windows Middle Tier Nodes.

When you add a node without copying configuration from an existing node, Cloud Manager fetches passwords from the password group that is mapped to the environment. Such auto-filled passwords cannot be edited from Cloud Manager.

Adding a Search Stack Node

This is an example of adding a search stack node to an environment.

This example illustrates the fields and controls on the Manage Node page for adding a Search Stack node.

You must select at least one feature. Elasticsearch and Kibana (or OpenSearch and OpenSearch Dashboards) can be added in the same node.

For information on adding a node for an environment with a search cluster, see Managing Search Clusters.

Refer to the section on Creating Topology for more information. See Adding Search Stack Nodes.

Adding a Middle Tier Node

This is an example of adding a middle tier node to an environment.

This example illustrates the fields and controls on the Manage Node page to add a Linux middle tier node.

In the Settings section, select the location of the Application DPK.

• Object Store

  When you select Object Store, the DPK Object Name drop down list will display all the application DPK files in Object Store.

  This example illustrates the fields and controls on the Manage Node page where the Application DPK location is Object Store.

  

• File Server

  If you manually copied app home and cust home to the file server provide the relative path to the file server.

  This example illustrates the fields and controls on the Manage Node page where the Application DPK location is File Server.

  

Adding Additional Middle Tier Nodes

This example illustrates the fields and controls on the Manage Node page for adding an additional Linux middle tier node.

Expand the sections.

Removing Nodes

To remove a node:

1. Click the Related Actions button corresponding to the environment.

2. Select Manage Node.

3. Select Remove action.

4. Select Type.

5. Available Nodes will be displayed.

   Note: Database node can not be deleted.

6. Select the node to remove.

7. Click Submit and confirm.

This example illustrates the fields and controls on the Manage Node page for removing a node.

Stopping Nodes

To stop a node:

1. Click the Related Actions button corresponding to the environment.

2. Select Manage Node.

3. Select Stop action.

4. Available Nodes will be displayed.

   Note: Database node can not be stopped.

5. Select the node or nodes to stop.

6. Click Submit.

This example illustrates the Manage Node page to stop a node.

Starting Nodes

To start a node:

1. Click the Related Actions button corresponding to the environment.

2. Select Manage Node.

3. Select Start action.

4. The Activate toggle is available for any nodes in a stopped status.

5. Select the node or nodes to start.

6. Click Submit.

This example illustrates the Manage Node page to start a node.