© Aaron Engelsrud 2019
A. EngelsrudManaging PeopleSoft on the Oracle Cloudhttps://doi.org/10.1007/978-1-4842-4546-0_6

6. Creating and Managing Topologies

Aaron Engelsrud1 
(1)
Saint Paul, MN, USA
 

The previous chapter focused on the repository and the functionality available from PeopleSoft Cloud Manager to simplify and automate the process of downloading and managing application packages. This chapter will focus on how you can design and manage the infrastructure on which those application packages will run. Cloud Manager uses the concept of topology to help define the various components within your PeopleSoft environment.

During the process of creating a new topology, you will determine how many nodes your PeopleSoft environment will run on, what operating system those nodes will run, the computing power of each node including CPU (virtual CPU) and RAM, and what PeopleSoft components are installed on each of the nodes. Your business requirements may dictate that your PeopleSoft environments include a Linux node for mid-tier components, one Windows node for PeopleSoft client tools which are used for development and updating your system, and a separate Linux node for the database. Within the Cloud Manager Topology, you can define and control these deployment features and provision the environment the way you need. Along with creating custom topologies to meet your needs, PeopleSoft Cloud Manager also comes with three topologies predefined for your use: Lift and Shift, PUM Fulltier, and Lift and Shift – DbaaS.

Accessing the Topology Home Page

To access the Topology home page, start by logging in to PeopleSoft Cloud Manager application with your administrative user. Once you are logged in, from the PeopleSoft Cloud Manager home page, click the Topology tile. This will open the Topology home page. Figure 6-1 highlights the Topology tile on the PeopleSoft Cloud Manager home page.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig1_HTML.jpg
Figure 6-1

Topology tile on the Cloud Manager home page

On the topology page, you will see that you have access to the three delivered topologies, you can clone existing topologies, and you can also create new topologies. Each of these functions will be covered in detail in the following sections and is shown in Figure 6-2.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig2_HTML.jpg
Figure 6-2

Three delivered PeopleSoft Cloud Manager Topologies

What Is a Topology?

A PeopleSoft Cloud Manager Topology does the following:

  • Defines the infrastructure layout of the PeopleSoft environment that will be created in the Oracle Cloud

  • Allows the administrator to choose what operating system the node will run on

  • Determines how much virtual CPU and memory are allocated to each node within the topology

  • Indicates which PeopleSoft components are installed on each node within the topology

Topologies are used within PeopleSoft Cloud Manager to help administrators create environments that meet the needs of the users of that environment. Administrators may create a development topology that is small and consists of only one node, a test topology that can be used when test environments are needed, and a production topology that consists of multiple nodes that are bigger and more powerful than the developer topology allows for. This provides added functionality, consistency, and reusability to PeopleSoft Cloud administrators and makes provisioning environments across the enterprise more straightforward.

Delivered Topologies

PeopleSoft Cloud Manager comes delivered with three unique topologies that can be used in the process of instantiating new PeopleSoft environments in the Oracle Cloud. These three topologies are Lift and Shift, PUM Fulltier, and Lift and Shift – DbaaS. Each of these topologies has a distinct use case and specific purpose. Additionally, these provided topologies can typically be used as a good starting point in creating a new custom topology that better meets the needs of your organization. Let’s explore each of these delivered topologies in more detail.

To access the node specific detail within each of the delivered topologies, you can get there by clicking directly on the row containing the name description of the topology you would like to see in more detail. This will bring you to the Topology Definition page. This page provides detail as to how many nodes are defined within topology, the environment type of the node, the size of each node, the operating system of each node, and the disk space of each node.

Lift and Shift

The Lift and Shift topology is delivered with three nodes predefined. A Middle Tier, a Database Tier, and a node for the Peoplesoft client. Unlike topologies that employ a single full-tier node, the Lift and Shift node breaks out the Middle Tier and the database on to separate nodes within the topology. Each of these nodes serves a distinct purpose in the environments created using this topology. You will notice that while you are able to delete our custom created topologies, you cannot delete the Lift and Shift topologies that are used for the lift and shift process, and the Delete button at the top of the page is grayed out and not accessible. Figure 6-3 shows the Lift and Shift topology definition and corresponding environment types.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig3_HTML.jpg
Figure 6-3

Lift and Shift topology

Middle Tier Node

If you click the node name, Environment Type in the Topology Definition page, you can see the specific detail about that node. In this case the Middle Tier consists of a Linux host operating system providing the middle tier PeopleSoft components including an appserver, webserver, and process scheduler. These components are built on a size small host (1 OCPU and 15GB RAM) and 100GB of disk space. Currently, it is not possible to remove individual components, such as the appserver or webserver, from the middle tier environment type. Figure 6-4 provides the detail included in the edit node dialogue.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig4_HTML.jpg
Figure 6-4

Lift and Shift – Middle Tier

Database Tier Node

The Lift and Shift Database node consists of a Database environment type build on a Linux host. This host is sized small with 75GB of disk space (Figure 6-5).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig5_HTML.jpg
Figure 6-5

Lift and Shift – Database Tier node

PeopleSoft Client Node

The third node in this topology is the PeopleSoft Client node. This node consists of a node running the Windows operating system and the PeopleSoft Client tools environment type. The size of this host is small and allows for 30 GB of disk space (Figure 6-6).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig6_HTML.jpg
Figure 6-6

Lift and Shift – PeopleSoft Client node

PUM Full Tier

The PeopleSoft Update Manager (PUM) Fulltier topology is a delivered topology that consists of one Linux full-tier node and one Window PeopleSoft Client node. This topology is well suited to provisioning PeopleSoft Images for PeopleSoft Update Manager applications. It is a simple and straightforward topology that provides the necessary components to quickly and easily spin up a PeopleSoft environment from a downloaded PeopleSoft Image. Figure 6-7 shows the PUM Fulltier Topology Definition.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig7_HTML.jpg
Figure 6-7

PUM Fulltier

Full Tier

The full-tier node of the PUM Fulltier topology consists of a Linux host running the Full Tier environment type. This means that an appsever, webserver, process scheduler, and database will all be deployed on this one virtual machine. The size of this node is small, and the host is allocated 100GB of file space (Figure 6-8).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig8_HTML.jpg
Figure 6-8

PUM Fulltier – Full Tier

PeopleSoft Client Node

The second node in the PUM Fulltier topology is a PeopleSoft Client node. This node runs the Windows operating system and deploys the PeopleSoft Client environment type. The size of this host is small and is allocated 30GB of file space. Once deployed, this Windows workstation is accessible via Remote Desktop Manager and can be used for development tasks through PeopleSoft Application Designer and Datamover or update tasks with Change Assistant (Figure 6-9).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig9_HTML.jpg
Figure 6-9

PUM Fulltier – PeopleSoft Client

Lift and Shift – DBaaS

The third topology delivered by PeopleSoft Cloud Manager is the Lift and Shift – DbaaS topology. This topology is designed specifically for Lift and Shift applications that are going to use Oracle Database as a Service for the database layer of the PeopleSoft application stack. Like the regular Lift and Shift topology, the Lift and Shift – Dbaas topology consists of three separate nodes: a middle tier node, a Database as a Service node, and a PeopleSoft Client node. Figure 6-10 shows the Topology Definition for the Lift and Shift – DBaaS delivered topology.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig10_HTML.jpg
Figure 6-10

Lift and Shift – DbaaS

Middle Tier

The Lift and Shift – DbaaS topology Middle Tier consists of a node running the Linux operating system. This is a small-sized node with 1 OCPU and 15 GB of RAM; the node has also been allocated 100 GB of disk space (Figure 6-11).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig11_HTML.jpg
Figure 6-11

Lift and Shift – DbaaS – Middle Tier

Database as a Service

The second node in this topology is the Database as a Service node . Like the middle tier node, this node also runs the Linux operating system. This node is sized small, with 1 OPCU and 15 GB of RAM along with 100 GB of disk space (Figure 6-12).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig12_HTML.jpg
Figure 6-12

Lift and Shift – DBaaS – Database as a Service

PeopleSoft Client

Like the other topologies that come delivered with PeopleSoft Cloud Manager, the Lift and Shift – DbaaS topology comes delivered with a Windows-based node to allow for PeopleSoft Client tool access. This is a small-sized host, with 1 OPCU and 15 GB of RAM and 30 GB of disk space (Figure 6-13).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig13_HTML.jpg
Figure 6-13

Lift and Shift – DbaaS – PeopleSoft Client

Creating a New Topology

You will find cases where the delivered topologies do not meet your needs. For example, none of the three delivered topologies would accurately define what you may need for a production, development, or test environment. To address this issue, you will need to create a new topology. To get started defining the components within your custom topology, you will need to log in to PeopleSoft Cloud Manager, and click the Topology tile on the home page. From the main topology page, click the Add New Topology button at the top of the page to get started (Figure 6-14).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig14_HTML.jpg
Figure 6-14

Add New Topology

Once you are on the Topology Definition page, you will need to provide the following two pieces of information:

  • Topology Name : This can be anything you like. It should clearly define what the topology provides in terms of infrastructure to the eventual instance. In our case we are calling this new topology “development (small).”

  • Description: Again, this can be anything you like; however, the more clearly you define the topology, the less opportunity there will be for accidental misuse. In this example, we are using “This is a small development instance with one middle tier node and one database node” as the description (Figure 6-15).

../images/471036_1_En_6_Chapter/471036_1_En_6_Fig15_HTML.jpg
Figure 6-15

Topology Definition

Now that you have your topology defined, you will next need to the appropriate nodes to your topology.

Adding a Node

To add a node, start by clicking the Add Node button at the bottom of the Topology Definition page. This will open the Add Node dialogue window. To complete this step and successfully add a new node to your topology, you will need to supply the following input:

  • Operating System: This is a drop-down box from which you can select either Linux or Windows. For this example, we are going to select Linux.

  • Environment Type: Here you need to select what type of node this will be. If your operating system is Linux, you will choose from one of the following choices: Database Tier, Database as a Service, Elastic Search Server, Full Tier, or Middle Tier. If you are creating a Windows node, you can only select PeopleSoft Client. For this example, we will select Middle Tier.

  • Sizing: Here you can choose from the VM sizes you have defined on the VM Size page in Cloud Manager Settings. PeopleSoft Cloud Manager comes delivered with small, medium, and large sizes defined. For this example, we will choose a small size VM.

  • Disk Space: You will need to provide how much disk space in gigabytes you want allocated to this node. Here, we will follow the standards set in the delivered topologies and allocate 100 GB.

  • Tiers: The tiers deployed in this instance are appserver, webserver, and process scheduler. You cannot, at this time, modify this setting.

  • Features: Is Cobol installed on this node or no? For this example, we will leave this set to No.

Figure 6-16 provides a view of the Add Node detail.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig16_HTML.jpg
Figure 6-16

Add Node detail

Once all the node settings are complete, click Done at the top of the window. You will now see this node added to the Topology Definition (Figure 6-17).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig17_HTML.jpg
Figure 6-17

Node successfully added

Finally, add any other nodes needed for this topology in the same manner, and then click Save in the top left corner of the Topology Definition page (Figure 6-18).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig18_HTML.jpg
Figure 6-18

Save the new topology

You should now see the newly created topology in the list of available topologies on the main Topology page (Figure 6-19).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig19_HTML.jpg
Figure 6-19

Newly created node, available for use

Topology Rules

For a topology to have all the components necessary to properly set up and configure a PeopleSoft environment, there are rules for the types of nodes that can or must be included within each topology. These rules are important as you start to define your custom topologies for use in your environment.

If you choose to have a node that is defined as full-tier node, PeopleSoft Cloud Manager will not allow you to have another full-tier node, nor can you have a mid-tier, database, or Database as a Service node included in the topology. You are free to add either a Window Client node or an Elasticsearch Server node if you like.

If you choose to have a node defined as a mid-tier node, given that the mid-tier node splits up some components found in the full-tier node, PeopleSoft Cloud Manager will not allow you to have a full-tier node. Additionally, in order to have a complete topology, you must include either a database or Database as a Service node in the topology. Here too, you can add a Windows Client node or Elasticsearch Server node as needed.

From a Database Tier perspective, if you allocate a database node, you are not able to have either another database node or a Database as a Service node as you are allowed only one database per topology. Additionally, you are not able to create a full-tier node with a database node created. Likewise, if you choose a Database as a Service node, PeopleSoft Cloud Manager will not allow you to allocate a database node nor another Database as a Service node. This is due to the fact that you can only have one database type node per topology. Here too you are unable to add a full-tier node to this configuration.

Editing a Topology

Editing a topology is a straightforward process. To get started editing a topology, first log in to PeopleSoft Cloud Manager and click the Topology tile on the application home page. This will take you to the main Topology page and your list of created topologies. Click the name of the topology you would like to edit to open the Topology Definition page (Figure 6-20).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig20_HTML.jpg
Figure 6-20

Click the topology you would like to edit

From here you can update the description of the topology, click directly on the nodes defined within the topology to modify their definition, or you can add nodes to the existing topology. To edit an existing node, click directly on the environment type to open the Edit Node dialogue window. For this example, we are going to expand the Disk Size of the middle tier node from 100 GB to 125 GB and then save the topology. Figure 6-21 highlights the Edit Node dialogue page.
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig21_HTML.jpg
Figure 6-21

Editing an existing node in a topology

Once the changes you desire are complete, click Done in the upper right corner of the page to save your edits to the node. You will see any changes you made reflected in the Topology Definition page. Click Save at the top of the page to finish saving your topology edits. You should see a message at the top of the page that your edits were successfully saved.

Cloning a Topology

In some cases, it may be faster for you to create a new topology by starting with an existing topology. This is called cloning. To clone an existing topology, complete the following steps:
  1. 1.

    Go to the the Topology home page, and select the existing topology you would like to clone by selecting the radio button to the left of the topology name.

     
  2. 2.
    Once the topology is selected, click the Clone button in the top left of the list of topologies (Figure 6-22).
    ../images/471036_1_En_6_Chapter/471036_1_En_6_Fig22_HTML.jpg
    Figure 6-22

    Select the topology to clone and click Clone

     
  3. 3.
    Next, provide the new topology with a name. In this example, we are going to clone the development (small) topology for use as a quality assurance (small) topology (Figure 6-23).
    ../images/471036_1_En_6_Chapter/471036_1_En_6_Fig23_HTML.jpg
    Figure 6-23

    Clone Topology

     
  4. 4.

    Click the Clone button in the top right corner of the window.

     
  5. 5.
    You will now see your newly cloned topology in your list of available topologies. From here you can edit the topology as needed (Figure 6-24).
    ../images/471036_1_En_6_Chapter/471036_1_En_6_Fig24_HTML.jpg
    Figure 6-24

    Newly cloned topology

     
  6. 6.
    To complete this exercise, we will click the new cloned topology and edit the description to more closely match the name of the topology and save the edits (Figure 6-25).
    ../images/471036_1_En_6_Chapter/471036_1_En_6_Fig25_HTML.jpg
    Figure 6-25

    Cloned and edited topology

     

Deleting a Topology

If you have topology that you no longer want available for use, you can permanently delete it from your list of topologies. However, if the topology is in use by any existing environment, you will not be able to delete the topology until the environment is no longer using the topology. To complete this task, click the name of the topology you want to delete, and then, directly from the Topology Definition page, you can completely delete the topology by clicking the Delete button at the top of the page. Once this button is clicked, you will get a confirmation message, and the topology will be removed from your list of topologies (Figure 6-26).
../images/471036_1_En_6_Chapter/471036_1_En_6_Fig26_HTML.jpg
Figure 6-26

Delete a topology

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.226.226.83