Start a web server - Web servers - Create and edit MIOapps

Chapter 3: Create and edit MIOapps

3.6 Web servers

3.6.1 Start a web server

Ctrl + Shift + W Stop a web server 3.6.2 Stop a web server Ctrl + C Create a MIOapp

container 3.2 Create a container Ctrl + Shift + C Delete the container 3.3.1 Delete a container Ctrl + L Lock the container 3.4.3 Lock a container Ctrl + Shift + L Unlock the container 3.4.4 Unlock a container Ctrl + A Allocate the

container’s slices 3.4.1 Allocate slices Ctrl + Shift + A Deallocate the

container’s slices 3.4.2 Deallocate slices

Ctrl + D Change description 4.1.1.3 Add or change a MIOapp’s description Ctrl + O Open the console 3.5.5 Open the console

Ctrl + I Import a MIOapp 4.2.5 Import a MIOapp Ctrl + U Deploy an upgrade 4.2.6 Deploy an upgrade

Chapter 2: Containers

2.1 Definition of a container

A container provides the resources you need to run a MIOapp in the cloud. It establishes two things: a name and a resource set, which MIOapp Manager uses to allocate physical resources, or slices. When you create a container, you choose the name of the container and one of a number of pre-defined resource sets.

The name identifies the container and is unique. Once you name a container, you cannot change it; MIOapps take the name of their container.

The resource set defines what resources MIOapp Manager should assign to the container and what engine it should use to run the MIOapp.

2.1.1 Containers and container contents

It is almost always useful in MIOapp Manager to distinguish between containers and MIOapps. The exception is the information pane, where both MIOapps and containers are listed under MIOapp.

A container has slices and an engine, but no metadata or configuration. A MIOapp has metadata and a configuration, but no slices or engine. Without slices and an engine, a MIOapp cannot run: MIOapps must be placed in containers for them to function.

Because you need containers to manage and run MIOapps, MIOapp Manager lists containers both with and without MIOapps under MIOapp in the information pane.

MIOapps in a container thus also appear in the information pane, but exported MIOapp files never appear until they are imported into a container.

In the MIOapp menu, MIOapp Manager identifies its container-specific features:

creating, deleting, clearing, locking, and allocating. Knowing the difference between a MIOapp and its container makes it clear how container-specific features behave and what they might affect, so you can better choose the correct feature to accomplish your goals.

2.1.2 Available containers

Because the point of a container is to hold a MIOapp, your available containers are listed under the MIOapp column in your information pane.

Most of MIOapp Manager’s real estate is devoted to giving you information about your MIOapps. If you do not have any MIOapps in your containers, MIOapp Manager

continues to report on your containers’ status alone. Status indicator symbols, beside

your container names, provide a visual indicator of your containers’ states. See table 2-A for a full list of possible status indicator symbols.

Table 2-A. Status indicator symbols

Symbol color Meaning More information

green Started, no reported problems 3.5.1 Start

white Stopped 3.5.3 Stop

green and white Started, automatic scaling

enabled for multiple slices 3.6.6 Configure automatic scaling

red Started, at least one reported

problem 3.5.2 Start in suspended mode

red and blue Recovered, at least one

unresolved host conflict 5.3.1 Ghost MIOapps blue Recovered, original host slice

now available 5.3.1 Ghost MIOapps

yellow Waiting for information 4.1.2 Refresh and show changes

Symbol shape Meaning More information

circle Primary MIOapp Chapter 3: Create and edit MIOapps

astroid Standby MIOapp 5.4 Hot standby circle with web

overlay Web server 3.6 Web servers

padlock Locked 3.4.3 Lock a container

no padlock Unlocked 3.4.4 Unlock a container universal no

symbol Not enough slices available in

quota to start 2.2.2 Quotas and availability

2.2 Processing

2.2.1 Slices

As discussed in 1.5.2 Resources and slices and 1.5.3 Resource sets, your MIOapp uses an assigned number of slices of computing power to perform its work. Your

organization’s MIOedge cloud is made up of a certain number of slices, with each slice being essentially equal in processing capability.

The Slices column in MIOapp Manager’s information pane refers to the total number of slices assigned to the container. For more information about slices assigned to a

container, see 4.1.3 View details.

2.2.2 Quotas and availability

The number of slices your organization can use at any one time has an upper limit:

the quota. Your quota is equal to the total number of slices your organization purchased from MIOsoft.

If your organization chose to divide its slices into environments, each environment also has a quota. If you do not have access to all of your organization’s environments, the quota you see in MIOapp Manager can be lower than your organization’s quota as a whole.

Only slices assigned to started MIOapps or slices allocated to a specific MIOapp count against your quota. Slices assigned to stopped MIOapps are not counted against your quota, so you can have more slices assigned to your stopped MIOapps than your quota has available.

MIOapp Manager does not count security server container slices or injector slices of size zero against the quota; see 2.2.4 Injectors for information about injectors.

You can get information about your quota situation from the environment pane.

2.2.2.1 The environment pane

The environment pane provides you with information about the quota status of your available environment(s) (fig. 2-1).

Figure 2-1. The environment pane

● Environment indicates the names of the environments you have access to.

● Quota indicates the slice quota of the environment.

● Used indicates the number of slices assigned to started MIOapps plus the number of slices allocated to specific MIOapps.

● Avail indicates the number of slices currently available for use by stopped, deallocated MIOapps. MIOapp Manager calculates your available slices by subtracting your used slices from your slice quota.

If you attempt to start a MIOapp which requires more slices than you have available, MIOapp Manager displays an error message and does not start your MIOapp (fig. 2-2).

When you start and stop MIOapps, the information in the environment pane updates automatically. You do not need to refresh MIOapp Manager to check on the current status of your quota.

Sorting the environment pane

MIOapp Manager defaults to arranging your environments in alphabetical order.

However, you can sort your list of environments by any of the information available in the environment pane.

To sort by a column in the environment pane:

● Click on the column header.

Your first click sorts the column least-to-most, or A-to-Z for the environment name.

● Click on the column header a second time to reverse the sort order.

MIOapp Manager indicates the direction of the current sort with an embossed arrow in the column header.

A downward-pointing arrow ( ) indicates a least-to-most, A-to-Z sort, while an upward-pointing arrow ( ) indicates a most-to-least, Z-to-A sort. The sort direction arrow does not appear until you sort by a column.

2.2.3 Slice allocation

Allocation allows you to set slices aside for use by a particular container. No other container can use the slices allocated to that container, even if the container you allocated slices to is stopped.

Slice allocation is useful when a critical MIOapp does not run constantly, such as a MIOapp that does your company’s billing, but runs only once a day at 2 a.m. and is stopped except during its early-morning run.

Because it is important to your company that the billing MIOapp run successfully, you

might want to ensure that the billing MIOapp always has enough slices to start, even if other MIOapps also try to start at 2 a.m.

To achieve this, you can allocate the billing MIOapp’s slices. Allocated slices can only be used by the MIOapp they are allocated to, and therefore are considered in use even if the MIOapp is not currently running. If you use a workflow server to allocate the billing MIOapp’s slices at 4:00 p.m., the workflow can email a notification if allocation fails and the recipient(s) can address the issue promptly because they receive the notification at a time when they are readily available.

This combination of slice allocation and the workflow server allows you to ensure that the billing MIOapp always has slices available to start while letting you use those slices during the day.

For information about allocating slices to a container, see 3.4.1 Allocate slices. For information about using a workflow server, see the MIOsoft Workflow Console™ User Guide.

2.2.4 Injectors

Most MIOapps use one or more injectors, which act as a gateway to the MIOapp. An injector accepts data from one or more data sources and then directs the subsequent flow of work to the MIOapp’s slices.

Any MIOapp slice can be an injector, even if it is doing other work.

However, injectors are most efficient when they do not have other work. The MIOsoft operations team creates these injectors by assigning a slice zero shares of work.

Because they have no work share, these slices cannot do anything except act as injectors.

Injector slices of size zero do not count against your slice quota.

2.3 Container types

MIOapp Manager allows you to work with three kinds of containers: MIOapp, workflow, and backup.

MIOapp containers are discussed in detail in 2.1.1 Containers and container contents.

Workflow containers are used to build automated MIOapp-managing operations, including container starts and stops, data loading, and report extraction. For more information about workflows, see the MIOsoft Workflow Console User Guide.

Backup containers are used to create independent backups of mqcapture and web

capture files. For more information about backup containers, see the MIOsoft Backup Console™ User Guide.

Each container type is restricted to its particular function. MIOapp containers can only be edited with MIOapp Console, workflow containers with Workflow Console, and backup containers with Backup Console. MIOapp Manager does not provide a function to change a container’s type.

The MIOapp Manager features described in chapters 3-5 apply to all container types, although instructions generally refer to MIOapp containers and MIOapps for simplicity.

Chapter 3: Create and edit MIOapps

3.1 Find MIOapps

3.1.1 View MIOapps

MIOapp Manager collects your MIOapps’ information into one primary window, allowing you to focus on access to and information about your MIOapps.

The bulk of your MIOapp Manager window is the central information pane, which is devoted to monitoring your MIOapps. It lists your existing containers in alphabetical order. If you have more than one environment available, MIOapp Manager shows the MIOapps from all of your environments by default.

A secondary window provides slice-level information about individual MIOapps; see 4.1.4 Viewing slice details for more information.

3.1.2 Select MIOapps

To perform any action on a MIOapp and/or container, you need to select it first.

To select a single MIOapp:

● Click the MIOapp in the information pane.

Selected MIOapps are highlighted in gray.

3.1.2.1 Select multiple MIOapps

You can select multiple MIOapps using the standard keyboard commands.

You can apply start/stop, allocation, and (un)locking functions to a multi-MIOapp selection.

To select multiple non-adjacent MIOapps:

● Hold down the Ctrl key and click each MIOapp you want to select.

To select multiple adjacent MIOapps:

● Select the uppermost MIOapp of the group you want to select, hold down the Shift key, and select the final MIOapp of the group.

MIOapp Manager selects all of the intervening MIOapps as well.

To deselect a MIOapp:

● Hold down the Ctrl key and click the each MIOapp you want to deselect.

To perform a function on a multi-MIOapp selection:

● Follow the instructions for performing the function on a single MIOapp, but with multiple MIOapps selected instead of one.

If you are starting, allocating slices, or deallocating slices, all of the MIOapps you select must have the opposite status–stopped, deallocated, and allocated,

respectively–for MIOapp Manager to perform the function.

If you are stopping, locking, or unlocking, you do not need all the selected MIOapps to have the opposite status for MIOapp Manager to perform the function.

3.1.2.2 View MIOapps by environment

You can also view MIOapps from one or a selected subset of your environments and hide the remaining MIOapps.

To view a subset of your MIOapps:

● Select only the environment(s) with the MIOapps you want to view.

You can select multiple environments using the standard Ctrl and Shift key methods described in the previous section.

As soon as you deselect an environment, MIOapp Manager hides its MIOapps. Showing and hiding MIOapps using the environments pane only affects their display in the information pane; their status and operation is unaffected.

3.2 Create a container

You can create a new container either by selecting a resource set or by duplicating an existing container.

If you choose to select a resource set, you can select from a list which includes the sets’ names and the numbers of resources each containers. You also see a version number associated with each resource set, which identifies the engine that MIOedge uses to run the container’s contents.

You create a container using the upper portion of the MIOapp section of the MIOapp menu (fig. 3-1), which is fourth from the top.

Figure 3-1. MIOapp section of the MIOapp menu

3.2.1 Select the new container's resource set

To create a new container and select its resource set:

1. Make sure no MIOapps are selected in the information pane.

2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead.

3. Click Create MIOapp container, Create workflow container, or Create backup container, prompting a resource set selection dialog (fig. 3-2).

Figure 3-2. Resource set selection dialog

4. Select the resource set you want your new container to use.

5. Click OK, prompting the Enter MIOapp container information dialog box (fig.

3-3).

6. Enter your new container’s name in the MIOapp name field.

You cannot have two containers with identical names. Your MIOapp name can include:

● letters: a-z and A-Z

● numbers: 0-9

● periods

● commas

● underscores

● hyphens

● plus signs

Other special characters and spaces are not allowed.

The OK button is enabled only after you enter an appropriate name for your container.

7. Click OK.

You return to MIOapp Manager, which pauses briefly while it creates the new container.

The new container appears in the information pane (fig. 3-4) in alphabetical order;

MIOapp Manager orders numbers by their individual digits, not by the number as a whole. If your quota has enough available slices to start the container, MIOapp Manager does so. If your quota does not have enough available slices, your new container is stopped.

Figure 3-4. New container in information pane

3.2.2 Duplicate an existing container

Duplicating an existing container is particularly useful if you plan to import or

compact an existing MIOapp into the new container. Duplicating the source MIOapp’s container ensures that your new container can support the incoming MIOapp’s

metadata and configuration.

Duplicating a container does not mean the new container uses the same slices as the source container; when the new container uses the source container’s resource template, it creates a separate (but identical) set of slices.

If you duplicate a container with a web resource, your new container’s web server uses the same port as the original web server. Web servers sharing a port cannot run at the same time; see 1.5.3.1 Identical web resources for more information.

To duplicate an existing container:

1. Select the container you want to duplicate. The container can be either started or stopped.

2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead.

Figure 3-5. Container name dialog

3. Click Create MIOapp container, Create workflow container, or Create

backup container, prompting the Enter MIOapp container information dialog box (fig. 3-5).

4. Enter your new container’s name in the MIOapp name field.

You cannot have two containers with identical names. Your MIOapp name can include:

● letters: a-z and A-Z

● numbers: 0-9

● periods

● commas

● underscores

● hyphens

● plus signs

Other special characters and spaces are not allowed.

The OK button is enabled only after you enter an appropriate name for your container.

5. Click OK.

You return to MIOapp Manager, which pauses briefly while it creates the new container.

The new container appears in the information pane (fig. 3-6) in alphabetical order.

MIOapp Manager orders numbers by their individual digits, not by the number as a whole. Apollo_11 precedes Apollo_8 because the leading 1 in 11 comes before 8.

Figure 3-6. Duplicate container in information pane

As with creating a container by selecting the resource set, your new container is started if your quota has enough slices to do so and stopped if it does not.

3.3 Delete

MIOapp Manager offers two kinds of deletion for your MIOapps and containers.

Clearing the container deletes the MIOapp completely, including all data and parts of the object model, but leaves the container intact. Deleting the container deletes the MIOapp and also the container.

Deletion is carried out from the deletion section of the MIOapp menu (fig. 3-7), which is at the bottom.

Figure 3-7. Deletion section of the MIOapp menu

3.3.1 Delete a container

Deleting a container permanently erases the container. If you delete a container with a MIOapp, all of the MIOapp’s data, metadata, databases, and local files are also deleted.

You cannot undo deleting a container or recover anything associated with the container from MIOapp Manager.

To delete a container:

1. Select the container you want to delete. The container must be stopped, deallocated, and unlocked.

2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead.

3. Click Delete container, prompting a confirmation dialog (fig. 3-8).

Figure 3-8. Container deletion warning pop-up

4. Click Yes.

MIOapp Manager pauses briefly while it deletes your container and removes it from the information pane. You can also use the keyboard shortcut Ctrl+Shift+C to delete a container.

3.3.2 Clear a container

Clearing a container completely deletes all data, metadata, and the configuration;

the container retains only its name, description, and slices.

When you clear a container, you must have enough slices available in your quota for MIOapp Manager to start it.

To clear a container:

1. Select the container you want to clear. The container must be stopped, unlocked, and you must have enough slices available in your quota for MIOapp Manager to start it.

2. Click MIOapp in the main menu bar, prompting the MIOapp menu. You can also right-click in the information pane instead.

3. Click Clear container, prompting a confirmation dialog (fig. 3-9).

Figure 3-9. Clear a container warning pop-up

4. Click Yes.

You return to MIOapp Manager; the container you cleared is now started.

If you click No, you do not clear the container and you return to MIOapp Manager.

3.4 Lock and allocate containers

Locking and allocation of containers allows you to control the level at which a

container’s contents can be accessed and whether a MIOapp has reserved slices so it can run, respectively. You apply these functions through the lock and allocate section

In document M I O app User Guide. a n a g e r. Version (Page 13-37)